GU - Workflow Configuration of Inbound IDOC
GU - Workflow Configuration of Inbound IDOC
com/ ©
https://www.youtube.com/@s4hclubforyou ©
Standard SAP IDoc interface uses ALE as the transfer mechanism and workflow functionality is used
to route a failed IDOC to a specific individual or workgroup.
Business data is exchanged with an external system using the IDoc Interface. The IDoc Interface
consists of the definition of a data structure and a processing logic for this. The data structure is the
IDoc. It is the exchange format that unites the communicating systems. Using IDocs you can define an
exception handling within the SAP System using SAP Business Workflow, without the need for the
data to already be an SAP application document.
To implement the distribution of business application processes and functions using ALE you need to
construct a logical Distribution Model of the whole system. Within the framework of this
configuration, customers can specify which applications are to run on which systems and which
messages are to be exchanged between the applications.
First step in the workflow configuration is to identify the IDOC type to be used for the inbound
processing
The main menu path to configure the IDOC can be found under Tools in SAP Easy Access Screen:
https://www.youtube.com/@s4hclubforyou ©
Identify the IDOC types for the inbound transaction, e.g.: ORDERS05 for orders, DELVRY03 for
shipments, etc
Make sure to use the latest available version, e.g.: for shipment, the latest would be DELVRY03
https://www.youtube.com/@s4hclubforyou ©
https://www.youtube.com/@s4hclubforyou ©
Identify the message type for the transaction, e.g.: ORDERS for orders, SHPCON for shipments, etc
https://www.youtube.com/@s4hclubforyou ©
In this screen, link the Message type with the Basic type
For a custom function module that will be used to process the inbound IDOC:
https://www.youtube.com/@s4hclubforyou ©
Check the 'Dialog allow', this will allow to run foreground and background if checked
Enter the Message Code if your setup required it, eg, you can setup different message code
that will be use in the FM to identify logic specific for Beaconlite vs MBP
Message Code can also be used to assign different org. unit for fallout notifications
https://www.youtube.com/@s4hclubforyou ©
Take note of the Receiver type, this will be use in subsequent fallout configuration
8. ALE configuration
Steps:
https://www.youtube.com/@s4hclubforyou ©
https://www.youtube.com/@s4hclubforyou ©
S_BCE_68000317_Organization Management
Organizational structure is created by assigning objects of the following types to each other:
Organizational Unit
Position
https://www.youtube.com/@s4hclubforyou ©
Job
Person
User
Task
https://www.youtube.com/@s4hclubforyou ©
This step is to setup the business user getting the error notification for any failed IDoc
https://www.youtube.com/@s4hclubforyou ©
https://www.youtube.com/@s4hclubforyou ©
https://www.youtube.com/@s4hclubforyou ©
Press Enter
Click on 'Yes'
https://www.youtube.com/@s4hclubforyou ©
https://www.youtube.com/@s4hclubforyou ©
Place the cursor on Standard task, and press the enter button
https://www.youtube.com/@s4hclubforyou ©
https://www.youtube.com/@s4hclubforyou ©
https://www.youtube.com/@s4hclubforyou ©
https://www.youtube.com/@s4hclubforyou ©
KU – customer
LI – vendor
LS – logical system
https://www.youtube.com/@s4hclubforyou ©
You should not use a user for this, user can come in and out, not stable
This is the default Agent that will get notified if the agent in the inbound Post processing
agent does not get resolved
https://www.youtube.com/@s4hclubforyou ©
https://www.youtube.com/@s4hclubforyou ©
You can execute workflow items by either "double clicking the item" or selecting the item
and clicking "Execute" button on the menu bar
This prohibits anyone else from taking the same work item
There are 2 kind of status buttons, one is white (square shape) and the other is blue (square
shape). Items in white has not been reserved by anyone.
If you determine that the item does not belongs to your business unit or for any other reason you are
not going to trouble shoot this item you MUST release the item
This will allow the work item to be place back in the queue
Place the cursor on the item, right click and select 'Replace' or use the (dotted square shape)button
on top of the menu bar.
To forward a workflow items beyond your team, place the cursor on the item, right click and select
'Forward'. A new popup screen will come up, you can enter the User in this box.
Double click on the work item to get more info for the fallout.
https://www.youtube.com/@s4hclubforyou ©
If there is a need to resend the IDOC, you must delete the existing fallout work item to delete it from
the queue
Click on the 'Delete flag' and the 'Yes' button to confirm the deletion.
XXXXXX usually is the message type, eg DESADV for delivery, ORDERS for order, etc
The FILL_DATA_XXXXXX is where you do data validation and build internal tables and variables
needed for subsequent process
The MAINTAIN_DATA_XXXXXX is usually where you see the main logic of the program, eg: to update
orders, delivery, purchase order, etc
23. FILL_DATA_XXXXXX
24. IDOC_STATUS_FILL
This is where you fill up the error messages you want display in the IDOC. You will need the status,
document number, message ID, message number, and detail messages (msgv1-4).
Status value:
https://www.youtube.com/@s4hclubforyou ©
50 - erster_statuswert_eingang
51 - fehler_bei_uebergabe
52 - beleg_unvollstaendig
53 - alles_ok
54 - fehler_in_der_bearbeitung