Workflow Configuration of Inbound data processing

Main Path: Tools->Business Communication


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:

            ALE > Inbound data processing
            Business Communication > IDOC setup
            Business Workflow > Org setup

WE30 - Identify the IDOC type


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
Make sure the IDOC has been released

WE81 - Identify the Message type


Identify the message type for the transaction, e.g.: ORDERS for orders, SHPCON for shipments, etc

WE82 - Link IDOC to Message type


In this screen, link the Message type with the Basic type

WE57 – Link IDOC to Function Module


For a custom function module that will be used to process the inbound IDOC:
            Use SE37 to create the FM
            Find one that is related and copy
            Create a new entry with the new custom FM

BD51 – Define FM attribute


If your custom FM would be using a 'Call Transaction', enter '2' in 'Input'
Check the 'Dialog allow', this will allow to run foreground and background if checked

WE42 – Define Process Code


For custom FM, create a new process code
Click on Logical message
            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

            Double click on the process code to get to this screen
            Click on the  ==> to go to next screen
            This setup will be use to configure the fallout event triggering

SWE2 – Event linkage

            Take note of the Receiver type, this will be use in subsequent fallout configuration

No comments:

Post a Comment