topic Re: Good Movement Inbound Interface Using IDoc in Application Development and Automation Discussions

Good Movement Inbound Interface Using IDoc

Former Member — Thu, 04 Oct 2007 08:16:03 GMT

Hi everyone,

I need help to create inbound interface for good movements using IDoc. I'm using XI as middleware. Here the functional design specification :

1. Good movements that will be considered :

- Good Receipt for PO

- Other Good Receipt

- Good Issues

- Transfer (Material to Material)

- Transfer (Plant to Plant)

- Reverse good movement document

- Physical inventory count difference

2. Using standard IDoc (Message Type - MBGMCR ; Basic Type : MBGMCR03)

3. Bapi that will be used is : BAPI_GOODSMVT_CREATE & BAPI_GOODSMVT_CANCEL

4. For physical inventory count differences using IDoc

- MATERIALPHYSINV_CREATEMULTIP01,

- MATERIALPHYSINV_COUNT01

- MATERIALPHYSINV_POSTDIFFEREN01

My Question is :

1. How we differentiate type of good movements ? (look point 1)

2. What process code that we must used? Is we need to create custom process code ?

3. Is we need create custom FM for process code ?

4. How we combine BAPI_GOODSMVT_CREATE & BAPI_GOODSMVT_CANCEL in one FM ?

5. At point 4 in specification, i need to using another idocs for physical count difference. Is this idoc can't combined with idoc MBGMCR ? How we use these idoc ?

Thank you and Regards,

Satria

Re: Good Movement Inbound Interface Using IDoc

Former Member — Thu, 04 Oct 2007 08:34:58 GMT

Hi!

1. By giving different parameters to the BAPIs. Check out transaction MIGO. You'll see A01 operation is for material income and R01 reference document is for purchase order. These fields can be located in the top left corner.

2. Mostly standards are giving the basic, but you always have to copy it to your needs. Then enter your function module in WE42 transaction to the given process

3. Of course you have to

4. You have to separate them with an IF statement maybe. Don't forget to set statuses for the IDoc and for correct processing, use BAPI_TRANSACTION_COMMIT statement also.

5. Pass

Regards

Tamá

Re: Good Movement Inbound Interface Using IDoc

Former Member — Thu, 04 Oct 2007 09:04:48 GMT

Thank you for your answer, Tamás. I want to ask again :

1. what process code standard that we can use to handle my case?

2. If we need to create custom FM, I'm still confused what parameter input/output/tables that i must create. How we define this parameter? Thank you

Regards,

Satria