Detail changes for release creation on schedule aggreements

Hi Experts,
Landscape:
-we have a standard ERP 6.0 system with an external EDI converter
-IDoc data exchange via RFC connection
-IDoc SAP standard (without modifications or add ons): message type: DELINS, basic type: DELFOR01
If we create a release on a schedule aggrement, all schedule lines in forecast comes out as expected.
When we delete some schedule lines, these lines exported to IDoc with quantity 0 and have an aggregation per week. So we have the following structure in IDoc:
E1EDK09 (head data)
|-E1EDP10 (pos data)
      |-E1EDP16 (schedule line): aggregation per week (IDoc field PRGRS = W), quantity 0
      |-E1EDP16 (schedule line): aggregation per day (IDoc field PRGRS = ' '), quantity 10
      |-E1EDP16 (schedule line): aggregation per week (IDoc field PRGRS = W), quantity 200
      |-E1EDP16 (schedule line): aggregation per week (IDoc field PRGRS = W), quantity 200
      |-E1EDP16 (schedule line): aggregation per month (IDoc field PRGRS = M), quantity 9000
So far so good. This looks fine.
But our standard EDI converter expect the IDoc data starting with days, weeks, months aggregation.  If the first schedule line with aggregation weeks are send, the converter expect all other schedule lines with aggregation per week or per month.
It is possible to change the release creation in the IDoc without coding in User-Exits, just with customizing?
regards,
Steffen
Edited by: Steffen Froehlich on May 3, 2010 1:31 PM (accidentally clicked on Post than Save button)

Hi,
   Go to MN04 transaction and maintain the "Date/Time" as 3 for the specific output type condition record as shown below:
   Test the scenario again with a new PO. Now, system wont generate the spool immediately after release and save in ME29N and the output will be "in process" mode (yellow signal). You can process the output in ME9F transaction to display and print.
Regards,
AKPT

Similar Messages

  • How to make a mass change for incoterms of a scheduling agreement at item level.

    Hi SAP Guru,
    There are many wrongly assigned incoterms in the scheduling agreement at item level by a user exit which was implemented recently in production. May i know if there is any way that we can revert those changes back to the original incoterms via mass change? I've tried to search over the internet and it seems like there is no posting about this issue before. Please help urgently. Thanks in advance.
    Regards,
    Shawn

    You can use the following sample to develop your usecase.
    Here, we would show menu items only for the nodes at level 3.
    You can also download the entire sample based on POJO at
    http://adfsampleapplications.googlecode.com/svn/trunk/TreeSampleApplication.zip
    The code is self explanatory.
    Let know, if you have any specific questions.
    <af:form id="f1">
    <af:treeTable value="#{bindings.continents.treeModel}" var="node"
    selectionListener="#{bindings.continents.treeModel.makeCurrent}"
    rowSelection="single" id="tt1" columnStretching="last">
    <f:facet name="nodeStamp">
    <af:column id="c1">
    <af:outputText value="#{node}" id="ot2"/>
    </af:column>
    </f:facet>
    <f:facet name="pathStamp">
    <af:outputText value="#{node}" id="ot1"/>
    </f:facet>
    *<f:facet name="contextMenu">*
    *<af:popup id="p1" contentDelivery="lazyUncached">*
    *<af:setPropertyListener from="#{bindings.continents.treeModel.depth}"*
    *to="#{pageFlowScope.CurrentDepth}"*
    *type="popupFetch"/>*
    *<af:menu text="menu 1" id="m2">*
    *<af:commandMenuItem text="View Districts" id="cmi1"*
    *visible="#{pageFlowScope.CurrentDepth == 2 ? true : false}"/>*
    *<af:commandMenuItem text="View Attractions" id="cmi2"*
    *visible="#{pageFlowScope.CurrentDepth == 2 ? true : false}"/>*
    *</af:menu>*
    *</af:popup>*
    *</f:facet>*
    </af:treeTable>
    </af:form>
    Thanks,
    Navaneeth

  • ABAP Changes for release ECC 5.0

    Hi experts,
    Can anybody please give me a list of all the changes in ABAP language, that are made from 4.6c to ECC5.0.
    Thanks in advance,
    Ravi Kanth Talagana

    Hi Ravi,
    First of all you need to check the 'UNICODE CHECKS ACTIVE' and initial steps to be taken care as follows:
    1)Replace the sy-repid with the variable v_repid by passing sy-repid to it.
    2)Replace the FM WS_UPLOAD/WS_DOWNLOAD UPLOAD/DOWNLOAD
      with the GUI_UPLOAD & GUI_DOWNLOAD.
    3)The assignment like IT_ITAB1[] = IT_ITAB2[] is not possible in the ECC 5.0 untill & unless both are of the similar structure. It gives a syntax error.
    4)Replace '09'(Hexadecimal character) by declaring a varibale and assigning the value of ABAP_CHAR_UTILITES=>HORIZONTAL_TAB which is in the class ABAP_CHAR_UTILITIES.
    Like these there are many things to be noted down.
    I can send you the detailed document on the ECC 5.0 and Unicode compliant details if you give your mail id so that I can attach the same to you.
    Reward if it helps you.
    Cheers,
    Sampath.

  • Significance of release creation profile

    Hi all,
    Can anyone explain with example the use and significance of release creation profiles in outline aggrement
    Thnks
    Gan

    Hi,
    Release Creation Profile
    Use: -
    The creation profile determines:
    - Which event triggers the creation of a scheduling agreement release (changes involving the lines of the overall schedule and/or the reaching of the next transmission date)
    - How the delivery dates are shown (aggregation and release horizon)
    - Whether
    Backlogs and Immediate Requirements are determined and shown in the scheduling agreement (SA) release Whether a tolerance check is carried out for SA releases that are created due to changes to the overall delivery schedule in the system
    Note: -
    The tolerance check is only carried out if lines of the overall schedule for an item have been changed and if you create SA releases using the release creation program (via Scheduling agreement ® Create SA release).
    Features: -
    A creation profile is defined on a plant-dependent basis and consists of the following areas:
    General parameters: -
    - Whether - and, if so, under what conditions - an SA release is generated (creation strategy).
    - Whether backlogs and immediate requirements are to be determined for the SA release type.
    - Whether or not the tolerance check is to be deactivated in the case of change documents created for SA releases with backlogs.
    Aggregation horizons: -
    - The Release Horizon for which released quantities are shown, and
    - The periods for which quantities may be aggregated.
    If your creation profile provides for aggregation, quantities and delivery dates set out in the lines of the overall delivery schedule stored in the system for a scheduling agreement are aggregated to form release schedule lines.
    If you use a creation profile without aggregation, or work without a creation profile, the schedule lines of the SA release correspond to the schedule lines of the overall delivery schedule for the scheduling agreement for the relevant period.
    Creation periodicity: -
    - Whether SA releases are to be created on a periodic basis (and, if so, at which frequency).
    Each time a scheduling agreement release is created, the system calculates the next creation date. Weekly and monthly releases are always created on a Monday (first workday of the period). The system takes the factory calendar as the basis for calculating the due dates for release creation.
    If you wish to create SA releases on a periodic basis, you should choose a creation strategy that includes Next date.
    Tolerance profile: -
    - Whether tolerances are are to be checked for scheduling agreement releases created as a result of changes to the overall delivery schedule. This allows you to specify that SA releases are only to be created following major changes to the overall delivery schedule.
    In the case of SA releases containing backlogs or immediate requirements, the system never checks tolerances.
    Activities: -
    You process creation profiles in Customizing for Purchasing under Scheduling Agreement ® Maintain Release Creation Profile for Scheduling Agreement with Release Documentation.
    You assign a creation profile to a scheduling agreement item in the Additional data.

  • Tables for Release strategies

    Hi ...
    I was referring to MM table doc , in that it is mentioned table EBELN & EBELP are for Purchase Order header / Line and BANFN & BNFPO are for PR header/ Line.
    But for release strategy ...people told me to refer CEKKO for PO and CEBAN for PR.
    does it mean that release strategy refers to different tables for execution ( and I believe these tables are used for release strategy purpose only and if Yes then at what point PO / PR data gets updated in these tables)
    Regards
    Suresh

    Hi,
    Please find release tables used in MM.
    EKAB       Release Documentation 
    EKEH        Scheduling Agreement Release Documentation 
    EKEK        Header Data for Scheduling Agreement Releases 
    T161E       Release Codes 
    T161F       Release Point Assignment for Purchase Requisition
    T161G       Release Prerequisite, Purchase Requisition 
    T161H       Fields for Release Procedure, Purchase Requisitio
    T161I        Determination of Release Strategy 
    T161S       Release Indicator, Purchase Requisition 
    T161U      Texts for Release Indicator 
    T163P        Release Creation Profile 
    T163S        Description for Release Creation Profile 
    T16FB        Release Indicators: Purchasing Document 
    T16FC        Release Codes 
    T16FD        Description of Release Codes 
    T16FE        Descriptions of Release Indicators: Purchasing Do 
    T16FG        Release Groups 
    T16FH        Descriptions of Release Groups 
    T16FK        Release Statuses 
    T16FS        Release Strategies 
    I think, it will help u.
    Ishu

  • Tables for Release Process

    Hi All,
    What are all the Tables associated with the Release Process.
    Advance thanks
    Regards
    Arjun

    EKAB   - Release Documentation 
    EKEH    - Scheduling Agreement Release Documentation 
    EKEK    - Header Data for Scheduling Agreement Releases 
    T161E   -  Release Codes
    T161F   -  Release Point Assignment for Purchase Requisition
    T161G   -  Release Prerequisite, Purchase Requisition
    T161H   -  Fields for Release Procedure, Purchase Requisitio
    T161I    -  Determination of Release Strategy 
    T161S   -  Release Indicator, Purchase Requisition
    T161T   -  Texts for Purchasing Document Types
    T161U  -   Texts for Release Indicator 
    T163P    -   Release Creation Profile
    T163S    -  Description for Release Creation Profile 
    T16FB    -  Release Indicators: Purchasing Document
    T16FC    -  Release Codes
    T16FD    -  Description of Release Codes
    T16FE     -  Descriptions of Release Indicators: Purchasing Do
    T16FG    -   Release Groups
    T16FH    -   Descriptions of Release Groups
    T16FK    -   Release Statuses
    T16FS     -   Release Strategies

  • Badi for release strategy me22n

    details Code for released status strategies on tcode me22n with function module .

    please check there is BADI ME_PROCESS_PO_CUST for PO Process and checks can be built in various method availble in BADI before PO release. For release strategy check user exit EXIT_SAPLEBND_002 .
    In case of any other details do revert back.
    anya

  • Zreports for vendor wise Delivery schedule release

    hi ,
    Can some one help me with codes for  the reports for the Delivery Schedule Release vendor wise. which shows vendor details , on titles, Schedule agreement Nos and then the material listed with the qty and targetted date.
    Kindly help
    regards
    Kim

    How to release directly from ME38 ?
    I tried in the path  delivery sche > Edit > generate Forc Sche
    but the msg below:
    Error generating release against scheduling agreement  (cause 2)
    Message no. 06857
    Diagnosis
    The function module for generating a scheduling agreement release (forecast delivery schedule or JIT delivery schedule) has run up against an error, causing processing to be terminated.
    In this case the cause of the error is 2.
    *System Response*
    The error may involve one of the following situations:
    1: The nature of the error cannot be specified precisely.
    2: The forecast delivery schedule or the JIT delivery schedule was generated but no message record could be generated.
    3: A document type for which the functions "Generate forecast delivery schedule" or "Generate JIT delivery schedule" are not defined may be involved.
    4: A material for which the function "Generate JIT delivery schedule" is not defined may be involved.
    5: A scheduling agreement that has not yet been released by all persons responsible may be involved.
    6: The factory calendar has not been maintained correctly.

  • Need some information regarding parallel release creation for VSA

    Hi ,
    Currently we are using the sequential release creation of vendor schedule agreement for both DELJIT/DELFOR (ME84)  and output message creation is" Only message for document"(ME9E) in backguond.
    But the nackground job takes longtime.
    so we are planning to do parallel release creation which reduce the time configuring parallel server.
    My question is that: if we go for parallel release creation in (ME84) do we need to go for output message (ME(E)as itemwise in each VSA" only message for SA release"

    Hi ,
    Currently we are using the sequential release creation of vendor schedule agreement for both DELJIT/DELFOR (ME84)  and output message creation is" Only message for document"(ME9E) in backguond.
    But the nackground job takes longtime.
    so we are planning to do parallel release creation which reduce the time configuring parallel server.
    My question is that: if we go for parallel release creation in (ME84) do we need to go for output message (ME(E)as itemwise in each VSA" only message for SA release"

  • Log for Release changes in PO

    Hi All,
    From which table i can get details of approval log for release stratergy in PO.
    My requirement is that i want to know  release changes history in Po From where i can get these details.

    Refer table EKKO or Check audit log using t.code AUT10 for ME29N.

  • Schedule line Release with help of release creation profile.

    Hello,
    Is it possible to create the schedule line release for scehule line automaticaly by heuristcs run with the help of release creation profile of external procurement relationship ?
    We can release the schedule line in product view.
    What is other way release the schedule line?

    Hi,
    Credit check is done to see if the customer has crossed his credit limit or not. Incase you want to forcefully release order we use [VKM1]. What is this got to do with the schedule lines??? Irrespective of whether the order is under credit hold or no the schedule line are determined the same way. Didnt understand the connection.
    Regards
    Nadarajah Pratheb

  • Want to change the Material group in Scheduling aggrement after creation?

    Hi Gurus,
    I want to change the Material Group in scheduling aggrement. I am able to change in PO but i m not able to change in Scheduling aggrement. It is in display mode after creation.
    I have checked the SPRO setting it is in optional entry only.
    Can anyone please help me. Wr we have to check the settings..
    Ot this is Standard SAP has provided.
    Please help me..
    Thanks
    Venkatesh P

    Hi,
    Thanks for your reply.
    EKPO is standard table. That we cannot change and that do end user want to chagne the material group.. This is not for one time.
    Please help..
    Thanks
    Venkatesh P

  • To make changes in  the subject of Email for PO Creation...

    Hi ,
            We have done configuration in NACE for simple mail to be sent when a PO is created . i want to change the subject of Email for PO Creation...
    Please help me in this regards
    Regards
    R/Ragu
    Useful answers will be rewarded

    Hi,
    In NACE, select your output type and double click on the option for Mail title and Texts in the navigation area on the left side of the screen. Here you can maintain the Subject for your E-mail.
    Cheers!

  • Where is the field release creation profile in scheduling agreement?

    Dear experts,
    I need to maintain release creation profile in Scheduling Agreement.
    please let me know where can I find this field in ME31L
    Regards,
    Shashidhar

    Found in More functions - Item details

  • The current iTunes 10.5 upgrade does not install on Windows 7 and indicates a faulty install package (error 2324). Advice or details on the release date for a proper fix?

    The current iTunes 10.5 upgrade does not install on Windows 7 and indicates a faulty install package (error 2324). Advice or details on the release date for a proper fix? I'm not able to roll back to the prior version, so I'm stuck in limbo.

    There have been a number of problems with installing the latest iTunes on Windows 7 64-bit machines during the last couple of weeks.  You might want to do a search on that topic and see if anyone has a solution.  There have been various versions of the problem but a lot related to errors in the download package or failure to download.

Maybe you are looking for