Reflexiones del trabajo realizado por centros

Use

You want (as part of an ALE scenario) to create a new model view in your central maintenance system's distribution model or enhance an existing model view.

Procedure

1. In the IMG, select SAP NetWeaver → SAP Web Application Server → IDoc Interface / Application Link Enabling (ALE) → Modelling and Implementing Business Processes → Maintain Distribution Model and Distribute Views.

Switch from display to change mode by clicking on Display <-> Change . 2. Click on the Create model view button and, in the window that then appears,

enter a short description of your model view and a technical name for identifying the model view. Confirm your entries with Enter and save to create the new model view.

3. Select your new model view and click on the Add message type button. In the window that now appears, enter both the sender's and recipient's logical system names and a message type of your choice. Confirm these entries with Enter; this will return you to the distribution model, where you can save the changes.

If you want to link a BAPI to the model view instead of a message type, click on the Add BAPI button. Add the sender's and recipient's logical system names (in other words, the method call's target system), enter the description (not the key) of the business object type you want to use and the appropriate method. Then confirm your entries with Enter.

4. To distribute the model view to a partner system, there must be outbound partner profiles with the partner for message type SYNCH. To check if these exist, select (in the distribution model's menu) Environment → Change partner profile. In the folder for partner type LS, search for an entry for your partner system and check the outbound parameters. If you do not find an entry for message type SYNCH, add one manually by assigning a recipient port containing an entry for the RFC destination leading to the partner system. The basic type has SYNCHRON as its key.

Hint: If the recipient system's logical system name is the same as the name of the RFC destination leading to it, you can have the system automatically create the outbound partner profiles for message type SYNCH and for all of the model view's other message types. To do this, select (in the distribution model's menu) Environment → Generate partner profiles.

Continued on next page

5. Distribute the new (or changed) model view by selecting the relevant entry in the distribution model and going in the menu to Edit → Model view → Distribute. If there is more than one possible recipient for the data being distributed and you only want to send the model view to one particular recipient, deselect the entries for the other recipients in the Distribute Model Views window that now appears.

You then receive a log that informs you whether the new (or changed) model view was successfully distributed or not.

6. If you have not already done so, create the outbound partner profiles for the message types you have just added to the model view. If there are outbound partner profiles for message type SYNCH (see step 4), you can have the system generate all the partner profiles for all the other message types (Environment → Generate partner profiles). If you create an outbound partner profile manually, you need to assign a recipient port with the appropriate RFC destination and a basic type, in addition to the message type.

Caution: When selecting the version, bear in mind the recipient system's release status, since the basic type needs to be recognized in the target system as well.

You also need to decide whether the IDocs should be sent immediately or later.

7. In order to be able to use your new (or changed) model view in an ALE scenario, you now have to create (or have the system generate) suitable inbound partner profiles in the target system. In the inbound partner profiles, you need an appropriate process code for the message type; this code must be linked to the function model or workflow for inbound processing. If you have the system generate the inbound partner profiles, you should check that it has assigned the right process code for your scenario.

BIT300 Lesson: Example: Material Master

Exercise 3: Master Data Distribution

Exercise Objectives

After completing this exercise, you will be able to:

• Send a material master

• Display an IDoc in the status monitor

Business Example

In the future, you want all material masters for the entire corporate network to be stored in the central system only and for them to be sent from there to the downstream sales branch and production systems.

Task:

Create a material master in the CORE logical system and send it in IDoc format to the PRODUCTION and SALES logical systems. Check the inbound and outbound processing for each in the status monitor.

1. Create the Basic Data 1 and 2 for material MATALE-## with a description of your choice. The material should belong to the Mechanical Engineering industry sector and to material type Finished product. The base unit of measure is a piece (PC).

Hint: “##” is your group number

2. First send your new material using the relevant transaction in the “Shared Master Data” instrument to the PRODUCTION logical system. How many master IDocs and how many communication IDocs were created?

Master IDocs

Communication IDocs

3. Send your material again without specifying a target system. How many master IDocs and communication IDocs were created?

Master IDocs

Communication IDocs

Continued on next page

4. How is the number of IDocs to be sent determined?

5. Display the outbound IDocs for message type MATMAS in the status monitor in the CORE logical system. What status do the IDocs have?

Hint: If you want to access one specific IDoc, enter the business object type StandardMaterial and your material number (MATALE-##) as the object keys on the status monitor's initial screen.

6. Next, display the IDocs in the status monitors for each of the two recipient systems: PRODUCTION and SALES. What status do these IDocs have?

Also check the material masters yourself.

BIT300 Lesson: Example: Material Master

Solution 3: Master Data Distribution

Task:

Create a material master in the CORE logical system and send it in IDoc format to the PRODUCTION and SALES logical systems. Check the inbound and outbound processing for each in the status monitor.

1. Create the Basic Data 1 and 2 for material MATALE-## with a description of your choice. The material should belong to the Mechanical Engineering industry sector and to material type Finished product. The base unit of measure is a piece (PC).

Hint: “##” is your group number

a) Select Logistics → Materials Management → Material Master → Material → Create (General) → Immediately.

b) Enter material number MATALE-##, select the industry sector Mechanical Engineering and material type Finished product and confirm your entries with Enter.

c) Select the views Basic Data 1 and Basic Data 2 and click Enter again.

d) Assign a material description of your choice and add the base unit of measure PC (piece). You do not need to make any entries in the Basic Data 2 view. Save to create the material master.

2. First send your new material using the relevant transaction in the “Shared Master Data” instrument to the PRODUCTION logical system. How many master IDocs and how many communication IDocs were created?

Continued on next page

Master IDocs 1

Communication IDocs 1

a) Select Tools → ALE → Master Data Distribution → Cross-Application

→ Material → Send.

b) Enter the following data:

Material MATALE-##

Message type MATMAS

Logical system PRODUCTION

Then select Execute .

c) One master IDoc and one communication IDoc have been created.

3. Send your material again without specifying a target system. How many master IDocs and communication IDocs were created?

Master IDocs 1

Communication IDocs 2

a) Select Tools → ALE → Master Data Distribution → Cross-Application

→ Material → Send.

b) Re-enter your material MATALE-## and the message type MATMAS but leave the Logical System field blank. Click on Execute . 4. How is the number of IDocs to be sent determined?

Answer: The number of communication IDocs depends on the number of receiver systems. If the recipient system is specified in the send transaction, only one communication IDoc is created. If you do not specify any recipient system, then the target systems are determined from the distribution model.

This could mean that more than one communication IDoc is created. The number of master IDocs always conforms to the number of master records that are to be sent.

BIT300 Lesson: Example: Material Master

5. Display the outbound IDocs for message type MATMAS in the status monitor in the CORE logical system. What status do the IDocs have?

Hint: If you want to access one specific IDoc, enter the business object type StandardMaterial and your material number (MATALE-##) as the object keys on the status monitor's initial screen.

a) Select Tools → ALE → ALE Administration → Monitoring → IDoc Display → Status Monitor.

b) In the Message type field, enter the value MATMAS and choose Execute .

c) Under Outbound IDocs, you should see your IDocs with status 03.

d) Select the entry for message type MATMAS and click on the Display IDocs button: you receive a list of all the IDocs for this message type.

e) Select one of your IDocs and click Display IDocs again.

6. Next, display the IDocs in the status monitors for each of the two recipient systems: PRODUCTION and SALES. What status do these IDocs have?

Also check the material masters yourself.

a) Select Tools → ALE → ALE Administration → Monitoring → IDoc Display → Status Monitor.

b) In the Message type field, enter the value MATMAS and choose Execute .

c) Under Inbound IDocs, you should see your IDocs with status 53.

d) Select the entry for message type MATMAS and click on the Display IDocs button: you receive a list of all the IDocs for this message type.

e) Select one of your IDocs and click Display IDocs again.

f) Select Logistics → Materials Management → Material Master → Material → Display → Display Current.

g) Enter your material number (MATALE-##) and click on Enter: both views are created.

Lesson Summary

You should now be able to:

• Describe the configuration of an ALE scenario for distributing material master data

• Distribute material masters

BIT300 Lesson: Using Change Pointers