Skip to Content
author's profile photo Former Member
Former Member

batch derivation before order print

Hi,

Our users assign batch numbers to the production order via the create batch button on the goods receipt tab page of the order. We have batch derivation set up to run at production order release and to derive the expiration date of the header mtl from the components. Our production scheduling profiles have been set to print the order at order release. When the user saves the released order, the event of release/saving triggers the shop papers to print. However the papers do not have the expiration date printed on them as the system cannot go thru the derivation condition records before the print. Is there any way to solve this? We are thinking of adding some delay between the release and the print to allow the system to run the derivation and fetch the date. Can we index the derivation record tables (std tables) to speed up the data access.

Thanks

Add a comment
10|10000 characters needed characters exceeded

Related questions

3 Answers

  • Best Answer
    author's profile photo Former Member
    Former Member
    Posted on Jun 12, 2012 at 08:57 AM

    Before adding customer own coding, did you check if a print mode change can solve it.

    If you choose print mode online, then priniting happen in parallel mode with posting to database. If you choose 'updated' for printing the print job should be started after data is saved to database, so it can be that then this is working.

    Don't know for sure, but you should try it first.

    BR Sabine

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Hi Senthil,

      I did find tat setting and it can even be changed in the production order while creation via the menu. However it seems as though we need to add a FORM routine and an update program for this to work. Thats what I could not locate. Do you know if this update program is above and beyond the print program which is assigned to the sapscript forms ?

      Thanks

  • author's profile photo Former Member
    Former Member
    Posted on Jun 12, 2012 at 12:09 PM

    Hi GS,

    We had similar issues earlier, when we were generating Serial numbers during order Release, and combining the 'Release & Print' orders through Production scheduling profiles option.

    Looks that the batch derivation data or Serial number gets generated during the order release, by which time the print relevant data is already extracted by the system... and hence, at times, the print outs miss the batch/serial numbers. Sure, a delay between the 'Release' and 'Print' could address this issue.

    We removed the 'Print while Release' option in production scheduling profile; and set up a separate batch job to pick the list of Released production orders and Print them --> and run this job every 15minutes ... No more issues! And no need for any custom coding.

    ==> Set up a variant in COHV (program PPIO_ENTRY) to pick the list of Released by not printed Production orders --> choose the option 'Print shop floor papers' --> Set up a batch job in SM36 using the program PPIO_ENTRY and the new variant --> manage the job in SM37.

    Please check and share your feedback.

    Thanks

    Senthil

    Message was edited by: Senthil Kumar Akash Sampath

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Hi GS,

      Thanks for the feedback.

      Table indexing, though sounding simpler, is a definite resource addition and cost addition; and unless we have compelling reasons, and if some SAP notes suggest that option, we better avoid it.

      Basis team could help us sharing more details of the concerns/issues with table indexing.

      Best Regards,

      Senthil

  • Posted on Jun 12, 2012 at 03:19 AM

    dear,

    you would engage the abaper for the new enhancement

    regards,

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.