I assigned my user ID as an agent for this example. However, this does not mean that my SAP inbox is flooded with iDoc error messages. A special workflow must be configured if you want the agent to be notified, but agent and agent types are mandatory parameters when defining partners in SAP. Hello ISURU FERNANDO, this is a great explanation, While I do the same with an order (BASIC TYPE: ORDERS04, Message type: ORDERS), the output is triggered at the order form, but in we20 the status is 02. How to solve it, please explain to me. Email ID: ramamurthypatnaik@gmail.com After you configure output determination and outgoing iDoc, you try to manually create the output of a sales order to ensure that all basic settings are correct. Shark. Such a beautiful job. Excellent explanation. Can you please help me with the outgoing idoc process once in your respective groups, the IDocs will then be aggregated according to the different statuses. The above view comes from a test system – in a production system, 216 outgoing IDocs in the 02 state are problem areas when transferring data to the port. If the treatment is successful, the system defines or updates the planning agreement in the planning agreement.

The IDoc is returned to the EDI database, which allows the status data to be updated. 2) How do I get idoc delivery information with item details? Click (1) Services for the object to open a toolbar with several useful features. Note that the system only checks for items that have not been rejected. If this search fails, the system checks only the customer/material number. This function adds the IDoc to the list of personal items. Now consider a real-world scenario in which outgoing iDocs should be transferred to an external system. In the B2B (business-to-business) process, order confirmations are returned to the EDI partner when EDI sales orders or purchase orders are created in SAP. This is the standard practice in most B2B EDI integrations. Similar to how we use change pointers for the distribution of master data, the output determination technique can be used to generate iDocs for transaction data. To send transaction data such as sales orders, purchase orders, deliveries, shipping confirmations, etc.

to partners and their systems, output types can be configured in SAP. Then select the sales order document type (XTRA) to find the corresponding output determination procedure. If you want to trigger a custom iDoc type, you can perform the following steps to configure the outgoing iDoc: Request routine 2 (order confirmation) is valid if the sales order is complete. If the sales order is incomplete or a credit block is defined, the order confirmation output is not triggered by the sales order. Very detailed. Great job!!. I have configured a similar output type determination for PO. But the Idocs fail with error code ME 760 on changing the purchase order compared to a custom field scenario.

We trigger Idocs in parallel with two different systems. For the first time, Idoc fails on a system and after the next switch to PO, it works perfectly. Output determination is now ready to generate EDI outputs from ZXRE sales orders under the X401 sales organization and the BP001 client to the OMS logical system. To test the scenario we created, navigate to the sales order creation transaction va01 and create a new XSTA document type sales order for customer BP0001 under X401 Sales Organization. In this step, we define the shipping time and transmission medium of the output type. Tip: In my experience, we42 is not an ideal way to find the process code, as the “Position” function can sometimes behave strangely. You may also need to find the process code from the iDoc message type. Therefore, I use the transparent table “TMSG1” directly through the se11 or se16 transaction to find the outgoing process codes and the type of message associated with them. Create a new sales order document or output from an existing sales order. The output must be in the yellow state (ready to be shipped). If the “Multiple Output” option is selected, the system allows the same output to be triggered multiple times from the same SAP document (sales order) to the same partner. To generate outgoing iDocs from ABAP programs, you must first find the outgoing iDoc that creates function modules like iDoc Message and iDoc Basic.

In the we57 transaction, you will find the FM that you can use to generate outgoing iDocs in an ABAP program. RSNASTED is the output processing program for various output media. EDI_PROCESSING is the ABAP processing routine for EDI output types. I think when a planning agreement is processed, some Idocs can be generated or triggered to send details. So I want information about these Idocs. Since I want to know what would be the segments, etc. that the Idoc would carry. If, for example.B. double-clicks on the 5500000139 object (the IDoc purchase planning agreement), the transaction opens automatically – in this case, the purchase planning agreement is opened in the ME33L transaction. If you click (7) IDocs in the previous screen, an ALV list of IDoc details opens. By default, the IDoc number, message type, status, etc. are displayed.

The following figure shows three messages from outgoing offenders. Orders sent from the OMS system are created using the standard order receipt iDoc, while the order confirmation is returned to OMS using the outgoing IDoc ORDRSP. As already mentioned, there are several ways to generate outbound iDocs in SAP. However, the standard practice for integrating the EDI sales order process is to use output determination that generates order confirmation iDocs from the purchase orders created. Specifically, the technique of recording the state of determination of the output is used. 1) Read the table from the user`s PC 2) Create the IDOC BLAORD message type with = IDOC_INBOUND_WRITE_TO_DB 3) Send RBDAPP01 (and the return) with the IDOC number from step 2 Go to the va03 transaction to view the sales order you just created. From the Output > main menu tools, select > Edit > display the expenses generated from the sales order. However, if you want to create files from outgoing iDocs directly from SAP, use the XML file or file port. You can also use the appropriate port type for your integration scenario, depending on how outgoing iDocs are transferred to the target system.

If you use a file port to transfer iDocs, you must also configure file names for outgoing iDocs. In this step, we create a new type of EDI output (ZOOC). We then fully configure the output determination procedure to trigger the EDI order output when an XTRA document type sales order is created in the X401 sales organization for customer BP0001. In other words, when a sales order is created, the system checks the records kept in these access sequence tables to determine whether or not the output should be triggered. You can create your own custom request routines in SAP. If the request routine returns the value 4 of the SY-SUBRC system variable, it limits the output of the sales order. In the above query, the routine output is removed by setting the SY-SUBRC to 4 if the sales order has a credit block of B or C (ABAP code lines from 25 to 28). The KU partner type is for customers and the LS partner type stands for logical systems. You can also trigger expenses for the KU partner type, as long as the customer is available as a listing in SAP.

If you want the system to determine the corresponding output based on the condition tables and access order, select this parameter. If this parameter is marked, the system automatically reads table B001 when creating or modifying a sales order and determines whether the output should be triggered. The procedure for output the XSTA sales order document type is X10000. We will use it in the configuration of the output determination procedure. In this step, we create an RFC destination for the SAP PO system. If you are using a different integration method (para. B HTTP), create another appropriate RFC target type. I need IDOC information for the delivery process that goes through the ME31L transaction. First of all, you need to determine what type of idoc message is related to the movement of goods….