cancel
Showing results for 
Search instead for 
Did you mean: 

How to use extended IDocs with DRF

Hello,

I've extended both LOIPRO and MATMAS IDoc into ZLOIPROMES and ZMATMASMES, which I get into MII respectively with RCCLORD report and BD10 transaction.

Next, I setup and activated DRF, but when I save / update a production order or when I distribute a material master via DRFOUT transaction, the standard LOIPRO05 or MATMAS04 IDocs are distributed.

How can I configure DRF to use extended IDocs instead of standard ones?

Thanks in advance!

Accepted Solutions (1)

Accepted Solutions (1)

RiccardoBrogi
Advisor
Advisor
0 Kudos

Hi albertopilatoderga,

as already suggested, check the partner profiles in WE20 and ensure that your IDoc custom extension has been maintained in the corresponding partner profiles settings.

R.

0 Kudos

Ciao Riccardo,

I've already checked WE20, seems configured correctly

Should I remove or specify the extension on the standard message types?

Thanks, A

RiccardoBrogi
Advisor
Advisor

Hi albertopilatoderga,

Any specific reason to use custom message types? Most probably the usage of standard message types extended with custom segment(s) would satisfy your needs. And this would simplify your job, since in this case you could use standard outbound implementations delivered with SAP MDG (that utilize, for example, MATMAS as basic message type to distribute Material Master - have a look to class CL_MDG_MAT_IDOC_DRF).

Otherwise you have to define you custom outbound implementation and develop corresponding class.

I also recommend you to run a search in the MDG community: you can find several threads useful info regarding this topic for example this one.

R.

0 Kudos

Thank you Riccardo, your comment has been illuminating!

I configured the extension to LOIPRO in WE82 and then in WE20, and it worked as expected.

Next question is what should I do in case of /AFS/MATMAS05 IDoc Type?

DRF Implementation 194_1 seems to refer to standard MATMAS, not the AFS one.

Regards, Alberto

RiccardoBrogi
Advisor
Advisor
0 Kudos

Ciao Alberto,

I'm not familiar with this specific message type but, assuming there is no pre-delivered implementation for DRF, you need at least to create your custom DRF outbound implementation and develop the corresponding outbound class.

This guide should give you some good hints.

R.

Answers (1)

Answers (1)

0 Kudos

Hello,

maybe you could refer to this topic in the Digital Manufacturing Cloud Integration Guide: Set Up Data Replication Framework (DRF)

You would need to replace the underlying message types in ALE and assignments in DRF with your custom, extended IDocs.

Best regards, Michael

0 Kudos

Thanks Micheal,

can you please point out where do i need to replace the message types? I checked both WE20 and BD64 and both already have the extended IDocs instead of the standard ones.

Regards,Alberto

0 Kudos

Hello Alberto,

as a disclaimer, I haven't set this up myself with custom IDocs before.

I understand you have adjusted steps 5 (WE20) and 6 (BD64) in the above documentation for your custom IDocs, so my only guess is, that the assignments in steps 7 and 8 still might point to a different distribution model that contains the standard IDocs.

Sorry, I don't have any more hints available right now. But this generic DRF topic (maps to step 😎 offers some notes about extended IDoc versions: Setting Up DRF Integration for MES Processes

Best regards, Michael

0 Kudos

Thank you Micheal,

I checked, as suggested in the paged you linked, the definition of the replication model

Unfortunately, I cannot find where to define the IDoc type, as illustrated in step 3 of this guide https://help.sap.com/viewer/9fbed5ee4a6745ed90e67716f93e3205/LATEST/en-US/667aa2e1747d49aeab7a8c3640...

Here, in the asterisk, is told that you can input an enhanced IDoc Type, which is exactly my case.

Thanks