Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

COND_A Master Data Distribution

Former Member
0 Kudos

How do I Distribute COND_A master data. Is there any standard t-code to do that?

1 ACCEPTED SOLUTION

ferry_lianto
Active Contributor

Hi Ram,

What is the issue here?

If you still want to use IDoc COND_A01 for sending and receiving purchase cost condition then you need to as follows (suggestion).

- Create custom program to collect purchase cost condition(s) and map to table parameter <b>PIT_CONDITIONS</b> which will be used to generate IDoc via FM MASTERIDOC_CREATE_COND_A.

- Setup the ALE and IDoc configuration to send/receive message type COND_A to/from XI system.

- XI system will perform data transformation from message type COND_A to legacy system format.

- For receiving purchase cost condition(s) from legacy system, XI needs to map, generate and send message type COND_A to SAP R/3.

- In SAP R/3, you can use standard functionality to post message type COND_A with process code <b>COND</b>.

Hope this will help and give an idea.

Regarsd,

Ferry Lianto

9 REPLIES 9

former_member214131
Active Contributor
0 Kudos

hello,

You can use the following FM ( SAP 46C ) for distribution:

MASTERIDOC_CREATE_COND_A

this FM is called in Tx: ME308 and in Prg.: RWVKP013

Hope this helps.

Best Regards, Murugesh AS

ferry_lianto
Active Contributor
0 Kudos

Hi Ram,

You may need to ask SD Functional folk to create new pricing report (t/code V/LA) with sending IDoc, message type and logical system paramaters available for input.

or you can copy an existing pricing report (t/code V/LD) into custom report/program and change below parameters to be displayed.

PARAMETERS sen_idoc(1) TYPE c           *NO-DISPLAY.
PARAMETERS p_mestyp  LIKE tbdme-mestyp  *NO-DISPLAY.
PARAMETERS p_logsys  LIKE tbdls-logsys  *NO-DISPLAY.

Once the report is available for you then the next step is to configure ALE and partner profile in order to generate IDoc COND_A01 from the pricing report.

You may find program RWVKP013 will not give enough selection screen compare with above pricing report. ONLY by material number.

Hope this will help.

Regards,

Ferry Lianto

Please reward points if helpful.

0 Kudos

Thanks for replies.

Murugesh,

unfortunately we are on 4.6B version

Ferry,

we donot have SD being used in this shop. Its handled in Legacy. But I do have to generate Idocs as we use MM. I mean I need to generate standard Idoc COND_A02 in MM-Purchasing area.

Please advice..

0 Kudos

Bonjour Ferry,

"You may need to ask SD Functional folk to create new pricing report (t/code V/LA) with sending IDoc, message type and logical system parameters available for input."

I tried in SAP 46C but i do not found the way to make sending IDoc, message type and logical system parameters available for input.

Is it possible for you to say if it is possible in SAP 46C ?

Cordialement,

Chaouki

ferry_lianto
Active Contributor
0 Kudos

Hi Ram,

You can use FM <b>MASTERIDOC_CREATE_COND_A</b> to generate the IDoc.

Please do search this FM where is being used in 4.6B,

perhaps you may find standard program available to be used.

Regards,

Ferry Lianto

Please reward points if helpful.

0 Kudos

They are not using Idocs so far. Basically I have to do everything from Triggering Idocs to sending to XI and then to legacy. I have to send / receive purchase cost conditions to / from legacy . Iam confused how to do this.

ferry_lianto
Active Contributor

Hi Ram,

What is the issue here?

If you still want to use IDoc COND_A01 for sending and receiving purchase cost condition then you need to as follows (suggestion).

- Create custom program to collect purchase cost condition(s) and map to table parameter <b>PIT_CONDITIONS</b> which will be used to generate IDoc via FM MASTERIDOC_CREATE_COND_A.

- Setup the ALE and IDoc configuration to send/receive message type COND_A to/from XI system.

- XI system will perform data transformation from message type COND_A to legacy system format.

- For receiving purchase cost condition(s) from legacy system, XI needs to map, generate and send message type COND_A to SAP R/3.

- In SAP R/3, you can use standard functionality to post message type COND_A with process code <b>COND</b>.

Hope this will help and give an idea.

Regarsd,

Ferry Lianto

0 Kudos

Thanks a lot Ferry. Iam new to this and your clarification will help.

0 Kudos

Hi Ram,

I am in the same situation now. I need to send the custom fields in the zsegment along with the IDOC COND_A02. I have created the segment and attached that with the Basic type COND_A02. As per the requirement the IDOC has to be triggered whenever there is a change in the pricing condition PB00 and DISCOUNT1 and DISCOUNT2 idocs has to be triggered.

Could you please help me understanding how these IDOCS will be triggered?

Good Day,

Thanks & Regards,

Uday S.