MediaWiki API result
This is the HTML representation of the JSON format. HTML is good for debugging, but is unsuitable for application use.
Specify the format parameter to change the output format. To see the non-HTML representation of the JSON format, set format=json.
See the complete documentation, or the API help for more information.
{
"batchcomplete": "",
"continue": {
"lecontinue": "20250105123615|163",
"continue": "-||"
},
"query": {
"logevents": [
{
"logid": 173,
"ns": 6,
"title": "File:Contact.png",
"pageid": 136,
"logpage": 136,
"revid": 814,
"params": {},
"type": "create",
"action": "create",
"user": "Unirab",
"timestamp": "2025-09-04T08:10:15Z",
"comment": ""
},
{
"logid": 172,
"ns": 6,
"title": "File:Contact.png",
"pageid": 136,
"logpage": 136,
"revid": 814,
"params": {
"img_sha1": "djmg8pm5t9in6sm3jwjqtmhk933f1c8",
"img_timestamp": "2025-09-04T08:10:13Z"
},
"type": "upload",
"action": "upload",
"user": "Unirab",
"timestamp": "2025-09-04T08:10:13Z",
"comment": ""
},
{
"logid": 171,
"ns": 0,
"title": "CRUD operations on purchase requisition in MM with Behavior Definition/Implementation I PURCHASEREQUISITIONTP",
"pageid": 135,
"logpage": 135,
"revid": 811,
"params": {},
"type": "create",
"action": "create",
"user": "Unirab",
"timestamp": "2025-06-04T08:35:24Z",
"comment": "Created page with \"[[Category:Behavior_Definitions_and_Implementations]] After reading this wiki entry, you should able to do operations Create and Cancel for purchase order goods receipt.<br /> <br />This is done by Entity Manipulation Language (EML) * https://learning.sap.com/learning-journeys/acquire-core-abap-skills/using-the-entity-manipulation-language_b378f225-0471-45bf-8b7a-f48d00e1bccb === Create purchase requisition with position === <syntaxhighlight line copy> DATA rap_pr_he...\""
},
{
"logid": 170,
"ns": 0,
"title": "Create and cancel operation for goods receipt purchase order with Behavior Definition/Implementation R MATERIALDOCUMENTTP",
"pageid": 134,
"logpage": 134,
"revid": 805,
"params": {},
"type": "create",
"action": "create",
"user": "Unirab",
"timestamp": "2025-06-03T11:54:35Z",
"comment": "Created page with \"=== Create goods receipt for purchase order === <syntaxhighlight line copy> DATA material_doc_header TYPE TABLE FOR CREATE r_materialdocumenttp\\\\materialdocumentheader. DATA material_doc_items TYPE TABLE FOR CREATE r_materialdocumenttp\\\\materialdocumentheader\\_materialdocumentitem. DATA material_doc_serials TYPE TABLE FOR CREATE r_materialdocumenttp\\\\MaterialDocumentItem\\_SerialNumber. CONSTANTS cid_mat_doc_hdr TYPE abp_behv_cid VALUE 'CID_MAT_DOC_HDR'....\""
},
{
"logid": 169,
"ns": 0,
"title": "Create and cancel operation for goods receipt purchase order with Behavior Definition/Implementation I MATERIALDOCUMENTTP",
"pageid": 133,
"logpage": 133,
"revid": 804,
"params": {},
"type": "create",
"action": "create",
"user": "Unirab",
"timestamp": "2025-06-03T11:53:37Z",
"comment": "Created page with \"=== Create goods receipt for purchase order === * [[CRUD_operations_to_create_goods_receipt_for_purchase_order_with_Behavior_Definition/Implementation_R_MATERIALDOCUMENTTP#Create_goods_receipt_for_purchase_order]] === Cancel for goods receipt for purchase order === <syntaxhighlight line copy> MODIFY ENTITIES OF I_MaterialDocumentTP ENTITY MaterialDocumentItem EXECUTE Cancel FROM VALUE #( ( MaterialDocument = keys[ 1 ]-PurchasingHi...\""
},
{
"logid": 168,
"ns": 0,
"title": "CRUD operations on purchaseorder in MM with Behavior Definition/Implementation I PURCHASEORDERTP 2",
"pageid": 132,
"logpage": 132,
"revid": 801,
"params": {},
"type": "create",
"action": "create",
"user": "Unirab",
"timestamp": "2025-06-03T11:12:38Z",
"comment": "Created page with \"Note: You can not create stock transfer orders with that. === Create Purchase Order === <syntaxhighlight line copy> DATA lt_header_data TYPE if_mm_pur_po_bil=>tt_proj_level_po_create. lt_header_data = VALUE #( ( %cid = 'CID_PURORDER_1' PurchaseOrderType = 'NB' \" cl_mmpur_create_test_pos=>get_valid_purchaseordertype( ) CompanyCode = lt_result[ 1 ]-CompanyCode \"'1710'...\""
},
{
"logid": 167,
"ns": 0,
"title": "Read on order stock - the sum of all open purchase order quantities for a material",
"pageid": 131,
"logpage": 131,
"revid": 794,
"params": {},
"type": "create",
"action": "create",
"user": "Unirab",
"timestamp": "2025-02-14T13:04:35Z",
"comment": "Created page with \"= Application = With transaction code MMBE you can read the on order stock for an material on plant level = Development = == With Function Modules == You can use FM \"MM_GET_PURCHASE_ORDER_QUANTITY\" to get the on order stocks for each positions in relevant purchase orders. Also you can use FM \"MATERIAL_UNIT_CONVERSION\" to convert the on order stocks in base unit of the material, e.g. to sum up all on order stocks for one unit and this should be the base unit of the mate...\""
},
{
"logid": 166,
"ns": 0,
"title": "IDoc message type PROACT",
"pageid": 130,
"logpage": 130,
"revid": 791,
"params": {},
"type": "create",
"action": "create",
"user": "Unirab",
"timestamp": "2025-02-07T20:48:14Z",
"comment": "Created page with \"{{Template:MetaDesc|General information for the IDoc message type PROACT(sending stocks etc.) and how the inbound IDoc can be processed and how the outbound IDoc can be created.}} [[Category:IDoc]] The PROACT is the IDoc message type for stocks and requirements data in an SAP. The outbound IDoc can be used to transmit data to a supplier for VMI (Vendor Managed Inventory / SMI (Supplier Managed Inventory). == General == '''Message type:''' PROACT <br /> '''Basic type:''...\""
},
{
"logid": 165,
"ns": 0,
"title": "Create and send e-mail with released class for cloud development",
"pageid": 129,
"logpage": 129,
"revid": 778,
"params": {},
"type": "create",
"action": "create",
"user": "Unirab",
"timestamp": "2025-01-08T17:18:24Z",
"comment": "Created page with \"[[category: code_snippets]] In all possible developments the released class \"CL_BCS_MAIL_MESSAGE\" should be used. In case the class is not available use the classic variant, see [[Create_e-mail_with_classic_classes_and_methods|here]]. <syntaxhighlight lang=\"abap\" copy> TRY. DATA(mail) = cl_bcs_mail_message=>create_instance( ). mail->set_sender( 'my@unirab.org' ). mail->add_recipient( 'r1@unirab.org' ). mail->add_recipient( iv_address = 'r2@unirab.org' iv_copy...\""
},
{
"logid": 164,
"ns": 0,
"title": "Virtual fields in CDS Views",
"pageid": 128,
"logpage": 128,
"revid": 770,
"params": {},
"type": "create",
"action": "create",
"user": "Unirab",
"timestamp": "2025-01-05T13:02:29Z",
"comment": "Created page with \"It is often necessary to supply data in a CDS view, as simple connections/relationships through CDS views are not possible and more complex coding is required. The calculation logic, in particular, is used to fill a field with a specific value. For performance reasons, you should use it as sparingly as possible. In my case, I developed an app with RAP and was able to map it completely using CDS views except for a few columns. == Introduction == Virtual fields are imp...\""
}
]
}
}