cancel
Showing results for 
Search instead for 
Did you mean: 

Why messages are being generated twice for Stopped SA releases?

Former Member
0 Kudos

Dear all,

I am working at the implementation of purchase scheduling agreements (LPA, with release documentation).

In our process, scheduling agreements are used in conjunction with MRP, which creates/updates/deletes delivery schedules. Messages for both JIT and Forecast releases are being automatically created by the system, based on predefined output creation profiles. As suggested by SAP, in case a planner wants to review a release prior to sending the message, it is possible to set a value in the SA item details (EKPO-STPAC, 'activate stop'), so that a release is generated yet not transmitted, till the planner approves the transmission.

My problem is that, even if the stop indicator is set, the system generates releases (transaction ME84) AND transmits them as soon as they are generated (LPH2, LPJ2 standard messages; I tested with print and mail media. Output condition records are set to 'immediate dispatch'). The produced SA Releases are marked as stopped - although already transmitted! This was not expected.

After the stopped releases are released (transaction ME89), a new message is created and transmitted for the same SA release....

I could not find any config settings that could prevent the system from transmitting messages when stopped releases are generated.

Any advice would be most appreciated.

Gianmarco

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Indicator T161N-OBJLG ('generate separate message per release') has to be switched on in IMG. This solves the issue.