VISIT WEBSITE >>>>> http://gg.gg/y83ws?6123988 <<<<<<
IDOCs are data containers with intelligence built in. Each IDOC contains one and only one business object. Customer Distribution Model. The Customer Distribution Model stores data that dictates which messages message types flow to which Logical Systems.
Many messages can flow to one Logical System, and one message can flow to several systems. This transaction is used very frequently in ALE. Filter object type and filter objects.
A filter object type is used in the Customer Distribution Model to impose a selection criterion on the message type flowing to a Logical System. A filter object type with a value associated with it is called a filter object. You can have multiple filter objects with different values for the same message type associated with that LS.
While determining the receiver s of a particular message based on the Distribution Model, ALE performs object filtering. Listings are a special filter object type occurrence and are also used to specify a selection criterion for distributing master data.
Listings are based on the SAP Classification system classes and characteristics , and are applicable only to Material, Customer, and Vendor master data. Once a list has been created, based on certain classification information using the ALE customizing menu, it is associated with an LS.
Change pointers. CD objects record the changes occurring to master data at a field level. ALE configuration provides a link between CD objects and change pointers. While CD objects are application-data-specific, the processing status of change pointers is message-type-specific. Also, the ALE change pointers are activated first at a general level and then at the message-type level.
ALE provides powerful capabilities to capture changes occurring to master data and to distribute them via the IDOC interface. This feature can be used to keep two or more systems synchronized with respect to master data. RFC destinations can be maintained using transaction SM Process codes. In this case, the process code identifies the application module that populates the IDOC with application data. Each process code is associated with a message type.
Message control and output type. The output records are stored in the NAST table. Message control uses the condition technique. To determine if an application document qualifies for output, search strategies are used through access sequences, output procedures, and requirements.
Once a message qualifies for output, message control modules use the parameters set in the condition type or output type to determine the timing of transmission and the medium of the message.
The output type also specifies the program or module to be invoked to create the output. Partner profile. A partner profile is an identifier for a system used for communicating messages. A partner profile brings together several ALE and EDI elements to define the parameters of communication between two or more systems.
Other than general information, you have to maintain inbound parameters, outbound parameters, and message control. The main parameters are message types, IDOC types, process codes, partner functions, application identifiers, message functions, output types, and ports. Other parameters also determine the mode of processing and error handling. It routes the specified messages through defined IDOC types to a given port after invoking the appropriate function modules for outbound processing.
It receives IDOCs of a specific type, and it identifies modules to post data to the application databases in the case of inbound interfaces.
The processes in the application layer and the ALE layer are completed on both the inbound and outbound processing sides. A check is made in the ALE distribution model that a message flow has been maintained for the input parameters. If there are filter objects in the distribution model that control this message flow, they are not evaluated. It is called with the message type to be dispatched. In return, you get a table containing all the potential recipients of this message type, as well as the associated filter objects.
Note that there may be several entries for one receiver in the table returned. If an exception is issued, an IDoc does not have to be created. Otherwise an IDoc does have to be created. You will find the receiving logical system in the rcvsystem field in a table entry.
The end result, that is, whether the receivers receives an IDoc and what the IDoc looks like, is only determined after all the filter objects for a message flow in the distribution model have been evaluated. This is carried out in the ALE layer. Structure of Control Records The control record consists of a field string for the structure edidc. The relevant fields are listed below; all other fields should be left with their initial values.
List of fields for the control record Field Description Comment mestyp Logical message type. Conveys the business meaning of the message. Mandatory field idoctp Basic structure of the IDoc. Identifies the layout set that uses this message. Mandatory field cimtyp Structure of customer extension. If the customer extends an SAP basic structure, he must give a name to the structure of his extension.
Mandatory field if customer has made an enhancement. Otherwise initial. Optional field. Data is stored in character format instead of binary format. IDOCs are independent of the sending and receiving systems. Skip to content. Report a Bug.
Previous Prev. Next Continue. Home Testing Expand child menu Expand. Great information! Skip to Content. August 7, 9 minute read. The object type and event of objects are linked as shown below: The data can be transferred by doing a binding between workflow container and event container.
Click on the mail activity in the workflow and following screen shot appears showing the mailing activity details: 2. BD Inbound Function Module is defined here as below: 2. WE Assignment of basic type message type, posting function module and object type created above: If you double click to see the details: 2. Alert Moderator. Alerting is not available for unauthorized users. Assigned tags. Similar Blog Posts. Related Questions. You must be Logged on to comment or reply to a post.
Gaurang Gujar. Hello Vivek, That's a great document something I was looked ng for. Thanks a lot for sharing the knowledge. Regards, Gaurang. Like 0 Share. Right click and copy the link to share this comment. Hi Gaurang, Thanks for reading my document, I hope it'll be helpful to you.
Thanks, Vivek. Former Member. Hi Vivek, Cool! Anjan Paul. Nice one.
Comments