Understanding Document Status Update
With the document status update feature, you can effectively track the status of all transactions in the following scenarios:
- Transactions that you initiate from your SAP ERP or SAP S/4 HANA system and send to suppliers on SAP Business Network throughh Managed Gateway for Spend and Network. In this scenario, you receive the Document Status Update.
- Transactions that you receive from suppliers on SAP Business Network into your SAP ERP or SAP S/4HANA system through Managed Gateway for Spend and Network. In this scenario, you send the Document Status Update.
You can conveniently access the status information for these transactions through the Transaction Tracker within the Managed Gateway for Spend and Network portal. For a comprehensive listing of the objects, sub-objects, and interfaces used to monitor the status of supported outbound and inbound transactions, you can refer to the tables provided below. These details are accessible through the transaction code SLG1.
Outbound Transactions (Document Status flows from SAP Business Network to SAP System)
| Transaction | Object | Subobject | Interface |
|---|---|---|---|
| Ship Notice Request | ARBCIG_NETWORK | SHPNOTICEREQ | DespatchedDeliveryNotification_Async_Out |
| FI-based ERP-initiated Invoice | ERPCC_INVOICE | ARBCIG_FIDCC2 | |
| Invoice Status Update | ISU | InvoiceStatusUpdateReq_Async_Out | |
| MM-based ERP-initiated Invoice | ERPCC_INVOICE | ARBCIG_GSVERF | |
| Order Enquiry | ORDER_ENQUIRY | ARBCIG_ORDENQ | |
| Payment Proposal | PAYMENT_PROPOSAL | PaymentProposalRequest_Async_Out | |
| Payment Remittance Request | REMITTANCE | ARBCIG_REMADV | |
| Product Activity Message | PRODUCT_ACTIVITY | ProductActivityMessage_Async_Out | |
| Purchase Order | PURCHASE_ORDER | ARBCIG_ORDERS | |
| Receipt Request | GOODS_RECEIPT | ReceiptDetailRequest_Async_Out | |
| Scheduling Agreement Release | SCHEDULE_AGREEMENT | ARBCIG_DELINS | |
| Service Sheet Response | SES_RESPONSE | ServiceEntrySheetResponse_Async_Out |
Inbound Transactions (Document Status flows from SAP System to SAP Business Network)
| Transaction | Object | Subobject | Interface |
|---|---|---|---|
| Component Acknowledgment | ARBCIG_NETWORK | COMP_ACK | ComponentAcknowledgeReq_Async_In |
| Component Consumption Request | COMP_CONSUMPTION | ComponentConsumption_Async_In | |
| Credit Memo | INVOICE | CreditMemoAttachProcessReq_Async_In | |
| Invoice | INVOICE | ARBCIG_INVOIC | |
| Liability Transfer | LIABILITY_INV | LiabilityTranserRequest_Async_In | |
| Order Confirmation | ORDER_CONFIRMATION | ARBCIG_ORDRSP | |
| PayMeNow | PAYME_NOW | ARBCIG_FIDCCH | |
| Product Replenishment Message | PRODUCT_REPLENISHMEN | ProductReplinishmentRequest_Asyn_In | |
| Remittance Advice | REMIT_ADVICE | RemittanceAdviceRequest_Async_In | |
| Sheet Service | SES_CREATE | ServiceEntrySheetRequest_Async_In | |
| Advance Ship Notice | ADVSHPNOTI | DespatchedDeliveryNotification_Asnc_In |
Maintaining Parameters for Document Status Update
To maintain the parameters for Document Status Update, follow these steps:
- Using the transaction code SPRO, navigate to Integration with Other SAP Components > Managed Gateway for Spend&Network for Buyer > SAP Business Network Integration > General Settings > Document Status Update.
- Expand the node and select IMG-Activity for Maintain Parameters for Document Status Update.
- In the Parameters – Document Status Update screen, select Modify and maintain the parameters shown in table below as per your requirements.
- Choose Save.
| Parameter Name | Description | Supported Values |
|---|---|---|
| TRIGGER_SUR | To send the status update request for proxy document. | Variable Name: TRIGGER_SUR Field Name: Leave it empty Number: 0000 Low: X (to enable) or leave it blank (to disable) |
| RESTRICT_SUCCESS_SUR | To prevent sending of success status update requests for Proxy document. | Variable Name: RESTRICT_SUCCESS_SUR Field Name: Leave it empty Number: 0000 Low: X (to enable) or leave it blank (to disable) |
| IN_IDOC_ERROR_STATUS | To maintain the final error status code of Ariba inbound IDocs. Use this parameter to read the errored out Ariba inbound IDocs and send error status update. This is used to send status update of inbound IDocs for PayMeNow and Order Confirmation. | Variable Name: IN_IDOC_ERROR_STATUS Field Name: Leave it empty Number: 0000 You can maintain more than one IDOC error status code by incrementing the value in the Number field, as needed. Low: Enter low value: 51 (for example) |
| IN_IDOC_SUCCESS_STATUS | To maintain the final success status code of Ariba inbound IDocs. Use this parameter to read the successful Ariba inbound IDocs and send the success status update. This is used to send status update of inbound IDocs for PayMeNow and Order Confirmation. | Variable Name: IN_IDOC_SUCCESS_STATUS Field Name: Leave it empty Number: 0000 You can maintain more than one IDOC success status code by incrementing the value in the Number field, as needed. ○ Low: Enter low value: 53 (for example) |
| IN_IDOC_SENDER_PART_NO | To maintain the partner number of the sender of Ariba inbound IDocs. This is used to send status update of inbound IDocs for PayMeNow and Order Confirmation. | Variable Name: IN_IDOC_SENDER_PART_NO Field Name: Leave it empty Number: 0000 Low: NWCCLNT520 (for example) |
Maintain Date and Time to Send Document Status Update for PayMeNow and Order Confirmation
To incrementally retrieve PayMeNow and Order Confirmation document status information from the previous fetch, it is essential to maintain date and time. This process is a one-time requirement for new customers. Whenever you execute the Document Status Update report, the system will automatically refresh the associated table with the most recent run date.
To maintain date and time and facilitate the transmission of document status updates for PayMeNow and Order Confirmation, follow these steps:
- Using the transaction code SPRO, navigate to Integration with Other SAP Components > Managed Gateway for Spend&Network for Buyer > SAP Business Network Integration > General Settings > Document Status Update.
- Expand the node and select IMG-Activity for Maintain Date-Time to send Doc. Stat. Upd. for PayMeNow and Order Confirmation.
- On the Change View "Table to store Proxy Parameters for ISU, PP, ERPCC, Recei screen, select New Entries.
- On the New Entries: Overview of Added Entries screen, from the Doc. Type drop-down, choose Document Status Update and enter values in the Date and Time fields.
- Choose Save.
Scheduling a Job for PayMeNow and Order Confirmation Document Status Update
You can opt to schedule a background job to transmit the status of Pay Me Now and Order Confirmation transactions from the SAP backend system to the SAP Business Network. Utilizing scheduled background jobs is strongly recommended for these reports.
In SAP, scheduling jobs follows a standardized process. Initially, you create a variant manually for the program. This variant is then employed in scheduling the background job. The specific program name linked to this task is ARBCIG_INBOUND_IDOC_SUR.
After you run the report, you can view the status of the report message status using the code SLG1 and using values for the object: ARBCIG_UTILITY and subobject: DOCUMENTSTATUSUPDATE, to filter the results.
You can also run the report ARBCIG_TRIGGER_DOC_STATUS_UPD manually to trigger document status update request.
To schedule a job for PayMeNow and Order Confirmation Document Status Update, perform the following steps:
- Run the transaction code SM36 – The Define Background Job Screen appears.
- In the Program field, enter ARBCIG_INBOUND_IDOC_SUR.
- Follow the instructions in the job scheduling wizard to schedule the program.
For more information on the Job Scheduling Wizard, refer to the SAP Help Portal.
Implementing the BAdI for Document Status Update
Customers have the option to utilize the available Business Add-In (BAdI) for the Document Status Update program (ARBCIG_INBOUND_IDOC_SUR). This BAdI can be configured to manipulate the data within the standard SUR (Status Update Request) message as needed.
To implement the BAdI for the document status update, perform the following steps:
- Using the transaction code SPRO, navigate to Integration with Other SAP Components > Managed Gateway for Spend&Network for Buyer > SAP Business Network Integration > General Settings > Document Status Update.
- Expand the node and select IMG-Activity for Business Add-Ins (BAdIs).
Implement the BAdI:
- BAdI name: ARBCIG_BADI_DOC_STAT_UPD
- Implementation methods:
- INBOUND_PRXY_PRE_PROCESSING: To pre-process inbound document status update.
- OUTBOUND_PRXY_PRE_PROCESSING: To pre-process outbound document status update.
Note
For more information about implementing a BAdI, refer to the SAP Documentation article, How to Implement a BAdI.