12. DESADV iDoc configuration to send Delivery confirmation

12. DESADV iDoc configuration to send Delivery confirmation

This configuration is done starting out in the NACE transaction and thus, creating a ZDEC message type for V2 application area, as shown in Figure-107. From Figure-108 to Figure-114, the settings for the different tabs comprising this new ZDEC message class in the NACE transaction are shown.



Figure-107 Creation of the new ZDEC message in the V2 application area of the NACE T-Code.


 

Figure-108 Configuring the access sequence for the new ZDEC output type in the V2 Application Area of the NACE transaction.


 

Figure-109 Setting the second tab for the new ZDEC output type in the NACE T-Code.


 

Figure-110 Setting the third tab for the new ZDEC output type.


 

Figure-111 Setting the fourth tab for the new ZDEC output type in the NACE T-Code.


 

Figure-112 Setting the fifth tab for the new ZDEC output type in the NACE T-Code.



Figure-113 Setting up the sixth tab for the new ZDEC output type in the NACE T-Code.


 

Figure-114 Setting the seventh tab for the new ZDEC output type in the NACE T-Code.



Within the Message Class Dialog Structure, select the folder corresponding to Process Routines and double-click it; Figure-115 appears to add the corresponding settings to the ALE Distribution processing medium.



Figure-115 Setup screen of the Processing Routines in the NACE Transaction for the new ZDEC message.


Within the same Message Class Dialog Structure, move to the Interlocutor Functions folder and, double-click on it to display the screen of Figure-116.


Figure-116 Configuration screen of the Interlocutor Functions in the NACE Transaction for the new ZDEC message.


Return to the main menu of the NACE Transaction to now access the Access Sequences button, which displays the screen of Figure-117.


Figure-117 Access Sequence Configuration Screen in the NACE Transaction for the new ZDEC message.


The V10000 output determination procedure within the V2 delivery application must contain the data shown in Figure-118 in order to find the type of message to be created:



Figure-118 Output procedure configuration screen in NACE Transaction for new ZDEC message.


 The Condition Record for ZDEC message, considering the LF delivery, the SH Partner Function Ship-to-party and the A (ALE) medium, is created as depicted in Figure-119.


 

Figure-119 Configuration screen of Condition Records in NACE Transaction for the new ZDEC message.


Once ZDEC message type has been configured, create a new entry for the ECOMMERCE logical system and the DESADV message type from WE20. It is important that DESADV message should not be used in any other logical system or it won’t work. This step is illustrated in Figure-120.


 

Figure-120 New entry for the E-Commerce logical system with the DESADV message type in WE20 T-Code.


Double-click on the DESADV message type to display the configuration screen shown in Figure-121.


Figure-121 Setting up the first tab of the DESADV message type in WE20 transaction.


And within the Message Control tab, set up the message that was previously configured in the NACE transaction, as illustrated in Figure-122.


 

Figure-122 Configuring the second tab of the DESADV message type in WE20 transaction.


Finally, add an entry in BD64 transaction for this message type, as shown in Figure-123, and then, display this DESADV message type in the main menu of such a transaction as shown in Figure-124.



Figure-123 Adding a new entry for the DESADV message type in BD64 transaction.



Figure-124 Deployment of the newly created DESADV message type in transaction BD64.



Returning to the processing of the Purchase Order and its respective delivery shown in Figure-125, see how this ZDEC message is processed correctly and thus, generates an iDoc which is shown in Figure-126.



Figure-125 Deployment of the delivery process in which a new ZDEC iDoc is generated.


 

Figure-126 General information of a new ZDEC iDoc generated as output to E-Commerce when delivering a Purchase Order.




    • Related Articles

    • 11. Setting up the ORDRSP iDOC for confirmation of the Sales Order

      To configure ORDRSP iDOC message in response to the creation of a Sales Order from the E-Commerce portal, the first step is to define a new message type in the NACE transaction: ZOEC for V1 application area. This ZOEC custom message is created in ...
    • 6. MATMAS iDoc configuration

      As mentioned in the configuration table of Figure-16, MATMAS iDoc is used for sending information from SAP Material Master to an External system, in this case, to the E-Commerce system. To start creating those messages, access the screen ...
    • 7. DEBMAS iDoc configuration

      As per table in Figure 16, DEBMAS iDOCs contain the customers’ master data. Initially, this iDOC is also configured within transaction WE20, Partner Profiles, by adding a new message type as illustrated in Figure-31. Figure-31    Adding the Message ...
    • 8. Setting up the iDoc to create SD QUOTATIONS

      As a standard, SAP does not support the creation of quote documents within the SD module, therefore, an iDOC Z must be setup based on the basic message type ORDERS05. This type of message is processed by a program (called ...
    • 10. ORDERS iDOC configuration for Sales Orders

      ORDERS iDOC is used to create a Sales Order. This iDOC is sent as a message to the SAP system from the E-Commerce portal. In SAP, the configuration of ORDERS iDOC begins in transaction WE20, on the Logical Systems part as an Inbound message, ...