Release Date and Time not updated in JIT schedule lines releases

[Former Member]

Hi,

I'm actually working on MM scheduling agreements.

When creating a JIT release, even though the LPJ1 output type is sent, the release date and time are not updated.

Without this update, I can not send other JIT releases as the release number stays to 1 and the system refuses to proceed a release allready treated.

I also send Forecast releases and for those the release date and time are updated.

I did the same customizing for the 2 release types:

set JIT indicator to 1 in the material master record

cross the U indicator ( Update print dependent data) for LPH1 and LPJ1

cross message per release for the procedure RMBEL1

For document type I copied LP MM scheduling agreement type and crossed the release document flag.

Would you have an idea on explaining why the release date and time are not updated for JIT schedule releases ?

Thanks

Etref

[satishbabu_bodepudi · Accepted solution]

Hi,

Have you assigned any release creation profile in vendor master and to scheduling agreement? This controls the print out of Jit or forecast.

Check below discussion for more details

http://scn.sap.com/thread/3414650

Regards

Satish

[satishbabu_bodepudi · Accepted solution]

Sorry for the wrong link shared above.

Here is the correct one

http://scn.sap.com/thread/3414643

Regards

Satish

[Former Member · Accepted solution]

Thanks Satish, I'm going to look at it and give a review once done.

[Former Member · Accepted solution]

Satish,

I followed what you wrote in the thread you gave me. It didn't solve the problem.

Some other elements,

-the requirement are 111 for LPJ1 and 109 for LPH1 (I activated requirement 111 as it wasn't done in standard)

-when I send FRC and JIT releases via me84, LPH1 appears in message per release (me38) only for FRC releases and LPJ1 only for JIT releases.

-the JIT indicator is set to 1 in MM02/MRP2 for my material

-the firm period to 10 days in additional data of scheduling agreement

Activating the release creation profile just filled the next JIT release in the creation/transmission tab of release overview in me38 but didn't allow the release to be filled with release date and time of release, the 2 mandatory condition for the system to increase release number on the next release creation.

You can see:

in caption 1 the release overview table,

in caption 2 the general parameters of the creation profile,

in caption 3 the aggregation horizon,

in caption 4 creation periodicity.

[satishbabu_bodepudi · Accepted solution]

Etref Pierre,

From your screen shot Caption4, You haven't given any value in 'No aggregation' field of JIT delivery schedule. Give some value Ex.3 days, so that the schedule lines falls under next 3 days will be sent without aggregating i.e., with the actual date & time of each schedule line. same applies for forecast schedule.

Regards

Satish

[Former Member · Accepted solution]

Satish,

I've given a value (3) to 'No aggregation' field but it doesn't change the problem.

I found something that solves the problem but I don't know the reason: activating internet release.

With that setting, the field EKEK-ABRDT is populated correctly.

Now, my 2 Idocs are sent and the system will release another JIT schedule in 24hours.

BUT my Idoc DELINS is not populated the right way:

-the IDOC coming from LPH1 is correct, it fills the forecast delivery schedule in the SD scheduling agreement

-the IDOC coming from LPJ1 is not populated correctly: SCRED value is 03 and ABHOR is blank (it is exactly the same IDOC as the one coming from LPH1, and the system response is 'Release no. 1 has already been allowed for in scheduling agreement XXX'. When I manually change ABHOR and SCREL, the IDOC intagrates successfully and JIT delivery schedule is populated in SD scheduling agreement.

In the document you gave me the link earlier, you seem to say it should work automatically... Per chance, do you have a solution ?

[satishbabu_bodepudi · Accepted solution]

Etref Pierre,

First of all, I havn't worked on scheduling agreements with IDocs. So I have to make an attempt with this and then I can tell something. As of I remember that is how i work with print out formats of LPJ1 & LPH1.

Regards

Satish

[Former Member · Accepted solution]

Thank you for your help anyway !

I have to figure out how to populate E1EDP10-SCREL and E1EDP10-ABHOR correctly.

Etref.

[satishbabu_bodepudi · Accepted solution]

Hi Etref,

Is Your issue solved or still facing the same?

Use message types DELJIT, DELFOR for message types LPJ1 & LPH1 respectively.

Creation profile which i explained in above link is sufficient to transfer date & times of schedule lines. The field ABHOR populates for message LPJ1(DELJIT) based on Jit horizon maintained in creation profile from SL release creation date.

Regards

Satish

[Former Member · Accepted solution]

Hi Satish,

I've implemented an exit to populate ABHOR and screl fields correctly.

I'm not using DELJIT message type, and I should have.

Whatever, the result is that my fields are correctly populated and send the right infos.

I've opened another thread on how to send schedule lines releases automatically. I've implemented a release creation profile and applied it to my scheduling agreement but can never see automatic releases.

Do you know if there is a program to run or a batch to set up ?

I hoped it would be strait working as in the profile I set up the releases to be sent each day or next to a modification.

Thanks a lot for the help you gave me allready.

Etref

[Former Member]

I noticed another thing while looking at the uncorectly processed IDOC (used to create a Sales Scheduling agreement from the Purchase one):

- the Idoc is incorrectly processed because of the release number not implemented

- the field E1EDP10-SCREL is recorded at 03 (forecast) and should be at 02 (JIT)

- the field E1EDP10-ABHOR is empty

[Former Member]

Hi,

Does JIT release is on Header or on Item ?

I believe once you trigger JIT (LPJ1) and if you condition record is set as 3 - send with application own transaction then you have to fulsh out output from T code:ME9E.

thanks.

[Former Member]

Hi Ravi,

how can I check at which level is my JIT release ?

For now, LPH1 & LPJ1 condition record are set as 4 send immediately so that I don't need to flush by ME9E.