Change in standard SD document flow

[Former Member]

Hi all,

I need to add some extra code in the SD flow.

The corporate request is to create a specific accounting document IMEDIATLY AFTER the goods issue of the materials in a delivery.

In more detail, we need to create a specific FI document IMMEDIATLY after a specific materials document (MKPF-MSEG) is created, and this materials document is created sometime between the goods issue and the saving of the delivery.

I must mention that I work in a 4.0B environment.

And another important mention is that the standard programs for creating/modifying a delivery (transaction codes VL01/VL02 - program SAPMV50A) were already modified in the past to meet some other specific corporate requirements.

So, it can be considered a solution to modify the standard once again, though I don't like nor agree with this method.

What is the most advisable method for accomplishing the task I described here?

[Former Member]

Hi all,

I need to add some extra code in the SD flow.

The corporate request is to create a specific accounting document IMEDIATLY AFTER the goods issue of the materials in a delivery.

In more detail, we need to create a specific FI document IMMEDIATLY after a specific materials document (MKPF-MSEG) is created, and this materials document is created sometime between the goods issue and the saving of the delivery.

I must mention that I work in a 4.0B environment.

And another important mention is that the standard programs for creating/modifying a delivery (transaction codes VL01/VL02 - program SAPMV50A) were already modified in the past to meet some other specific corporate requirements.

So, it can be considered a solution to modify the standard once again, though I don't like nor agree with this method.

What is the most advisable method for accomplishing the task I described here?

[Former Member]

Hi,

Have a look at the userexits available in delivery processing. I think it is called USEREXIT_SAVE_DOCUMENT in SAPMV50A

Trigger the process in here by calling a BAPI to create an accounting posting.

Otherwise, raise an event in the userexit that triggers a job to create the posting.

How does this sound ?

Kind regards

Colin.

[Former Member]

Colin, I tought about this but it does not seem to solve the task.

What I did was this: I simply put a break-point (BREAK USERNAME.) in those otherwise nice looking userexists. (USEREXIT_SAVE_DOCUMENT and USEREXIT_SAVE_DOCUMENT_PREPARE)

When the process of saving the delivery reached the breakpoint, I looked in the MKPF table to see if the material document that I'm particularly interested in already was created, and IT WAS NOT.

I then continue the execution and, at the end of the execution, the material document EXISTS in the MKPF table.

I need to trigger my action AFTER that material document was created (the material document corresponding to the goods issue).

Thank you for the hint.

[Former Member]

Ok,

Try it the other way.

Use a userexit in material document creation to check if the document is created from a delivery and fufils any other criteria you wish to have then perform your actions.

Kind regards

Colin.

[Former Member]

Colin,

I think your suggestion is worth the closest attention. Thank you very much.

[former_member374]

Hi CIOC,

You are thanking a poster for his answer.

Please next time also give him points.

See: /people/mark.finnern/blog/2004/08/10/spread-the-love

This time I did it for you.

Remember: When you ask a question you also assume the responsibility to assign points.

Please check your other questions and if the answers were good.

Spread the love and give some points.

Thanks in advance, Mark.