Schedule Lines deletion from Scheduling agreement

Hello all
There is a requirement of mass changes deletion of existing Schedlue lines from Schedling agreement ( from around 800 Scheduling agreement).
SAP version is 4.7(Which doesnt have MEMASSSA-std t-code for mass maintenance of scheduling agreement).
Please advise, how these can be deleted in bulk.
Thanks & Regards
Rajesh

Hi
Go to table :SE16 :
Enter :EKET
download to the excel file do the correction then upload the file to to the table.
Please check with your SAP ABAP team and with your Client
(or)
do it manuallly .go to me38 enter the sch.agreement no and delete the qty and save . it is time consuming
it willl take a day or Two.
This is the best solution
Regards
Ganesh

Similar Messages

Delivery before the schedule line date in scheduling agreement.

Hi All,
I have a situation where in I am using JIT delivery schedule for processing the delivery requirement from customer. In this, lets say, I have a schedule as 08/05/2009 for material A to deliver 1000 qty and the material is made available to me after production as of 07/05/2009 and I want to despatch the material on 7th only and not on 8th. The system does not allow me to do this.It allows me to make a delivery only on 08/05/2009.
Is there any alternative to this and is this SAP standard behaviour.

I think you can change the schedule line date in scheduling agreement itself and do the delivery.
regards,
Sudhir

Link between Delivery schedule line counter from PO and the material docume

Dear Gurus,
I have one PO with single line item having delivery schedule -
Material 1 -
delivery schedule 01.01.2009     2000
                                                     01.03.2009    5000
I have received quantity against this Po
I want to know where I can find the link between Delivery schedule line counter from PO and the material document
Best regards
Sar

There is no link from the MAterial document line item (Table Mseg) to the PO Schedule Line (EKET).
If this is for Evaluating an on time delivery or GR, you may consider the following approach.
PO details Po Date QTY
Sch1   01Jun2009   200
SCH2 08Jun2009   100
GR Details
GR1   01Jun2009   180
GR2   07Jun2009   110
GR3 09Jun2009      10
Calculate a *** total qty for the PO Line.
PO details Po Date CUMUL QTY
Sch1   01Jun2009   200
SCH2 08Jun2009   300
Calculate a *** total qty for the ontime GR.
PO details Po Date CUMUL PO QTY CUMUL GR on time
Sch1   01Jun2009   200                180
SCH2 08Jun2009   300                 290 (180+110) the 3rd GR was too late
Evaluate the PO SChedule Lines as follows:
Po SCL qty + CUMUL GR QTY - CUMUL PO QTY = ADJ GR ON Time Qty
SCH1 01Jun2009
200 + 180 - 200 = 180 on time for 01Jun2009 date ( 90% fill rate)
SCH2 08Jun2009
100 + 290 - 300 = 90 on time for 08Jun2009 date (90 % fill rate) the first 20 of the GR on 07Jun2009 went to fill the late, early date.
Best of luck !
SCH2 100 +290 - 300 = 90 on time for 07Jun2009 date

Text in the scheduling lines of a scheduling agreement.

hi,
is it possible to add text some where in the scheduling lines of a scheduling agreement (like how we can insert header text in the line item)??

yes.I agree with you that in all good processes schedules lines are automatically generated by MRP run.
On the other hand,some times due to incontigencies we are forced to manually add the schedule.At that time,my client wants to capture those incontigency reasons which he wants along with the schedule lines.
Please let me know whether SAP has got some way out for this issue.
Thanks.
Edited by: r.jeethendiran on May 12, 2011 5:46 AM

Difference between Scheduling lines and Delivery schedule

Hi SD Experts
can u say me the clear difference between Scheduling lines and Delivery schedule.
where we will maintain deliver schedule. whether delivery schedule is automatically created along scheduling agreements..
with regards
James

Hi James,
Schedule Lines: Has basically information realted to delivery scheduling in Sales Order level.
Delivery Scheduling: Is a process using which system will determine what are the different activities which need to be performed and time taken for each activitiy only after which the material can be delivered to the customer.
Delievry scheduling will be started only from the material availability date i.e., system will first determine the material avail date and then do scheduling. By default Standard SAP system does Backward Scheduling in case material availability falls beyond the required delivery date system will do forward schedluing
Delivery Scheduling consists of the following Basic activities:
We give deatils while creating order:
Order Creation Date
Required Delivery Date
Order date - Material availability date - Transportation Planning Date - Loading date - Goods Issue Date - Required Delivery Date
Time Between GI Date and required Delivery Date is called Transit Time
Time Between LoadingDate and GI Date is called Loading time
Time Between Material Availability Date and Loading Date consists of 2 components - Pick / PackTime and Transportation Planning Time
System has to calculate all this before it determines the confirmed delivery date.
Give your mail Id I have some Presentation I will send you across.
REWARD POINTS IF IT HELPS
Regards
Srini

Copy line items from Master Agreement to SubAgreement

Dear all,
As a requirement, we need to create a dummy line item at master agreement and subagreement level to be able to publish them to ERP without need
to complete line items (they are completed in ERP via a development).
We have created master agreement templates with a dummy line item but at subagreement level, templates are not available.
What we are trying to develop is a script on post_create at agreement level to copy line items from Master Agreement to SubAgreement. We are able to get Master Agreement line items and copy them to the SubAgreement, but the subagreement is not created. This is the code we are using:
import com.sap.odp.api.doccommon.masterdata.ValueListValueIBeanHomeIfc;
import com.sap.odp.api.doccommon.masterdata.ValueListValueIBeanIfc;
import com.sap.odp.api.doccommon.masterdata.ValueListTypeIBeanHomeIfc;
import com.sap.odp.api.doccommon.masterdata.ValueListTypeIBeanIfc;
import com.sap.eso.api.contracts.ContractIBeanHomeIfc;
Mst_agreementBean = doc.getParentIBean();
lineItemCollectionSub = doc.getLineItems();
lineItemCollection = Mst_agreementBean.getLineItems();
collectionsize = lineItemCollection.size();
colln = Mst_agreementBean.getCollectionMetadata("MA_LINEITEMS").get(Mst_agreementBean);
colln2 = doc.getCollectionMetadata("MA_LINEITEMS").get(doc)
newProject = Mst_agreementBean.getIBeanHomeIfc().createFromAnother(Mst_agreementBean);
newMember = colln.get(1);
// Get Values Line Item
assCat = newMember.getAcctAssignCategory();
actLimP         = newMember.getActualLimitPercent();
delAdCity       = newMember.getDeliveryAddressCity();
delAdCount    = newMember.getDeliveryAddressCountryRef();
delAdDist       = newMember.getDeliveryAddressDistrict();
//... (all fields included in the script)
// Create Line
newMember2 = newMember;
AgreementHome = IBeanHomeLocator.lookup(session, doc.getObjectReference());
AgreementHome.upgradeToEdit(doc);
// Set Values
newMember2.setAcctAssignCategory(assCat);
newMember2.setActualLimitPercent(actLimP);
newMember2.setDeliveryAddressCity(delAdCity);
newMember2.setDeliveryAddressCountryRef(delAdCount);
newMember2.setDeliveryAddressDistrict(delAdDist);
//... (all fields included in the script)
try{
colln2.add(newMember2);
AgreementHome.save(doc);
AgreementHome.downgradeToView(doc);
collectionbean = colln2.get(0);
logInfo("Value of collectionbeanSub " + collectionbean );
}catch (ApplicationException e){
logInfo("Error " + e.getClass() + ". " + e.getMessage());
When we try to create an Agreement under a Master Agreement (clicking Add on Agreement tab), following error message is shown related to the line in blue:
Facility=local4;sessionid=4e73bb8e73304d6284816f93f4e04522a7c387b; tenantid=#tenant.ecb#;username=LUGUELL; exception=Sourced file: inline evaluation of: ``// **   import com.sap.odp.api.doccommon.masterdata.ValueListValueIBeanHomeI ... '' : Method Invocation AgreementHome.save : at Line: 164 : in file: inline evaluation of: ``// **    import com.sap.odp.api.doccommon.masterdata.ValueListValueIBeanHomeI ... '' : AgreementHome .save ( doc )
Target exception: java.lang.NullPointerException: while trying to invoke the method com.sap.eso.contracts.ContractTypeBo.getVendorVisible()
of a null object returned from com.sap.eso.contracts.ContractCommonBo.getTypeBo()
;stacktrace=Sourced file: inline evaluation of: ``// *JLA*    import com.sap.odp.api.doccommon.masterdata.ValueListValueIBeanHomeI ... '' : Method Invocation AgreementHome.save : at Line: 164 : in file: inline evaluation of: ``// *JLA*    import com.sap.odp.api.doccommon.masterdata.ValueListValueIBeanHomeI ... '' : AgreementHome .save ( doc )
Target exception: java.lang.NullPointerException: while trying to invoke the method com.sap.eso.contracts.ContractTypeBo.getVendorVisible()
of a null object returned from com.sap.eso.contracts.ContractCommonBo.getTypeBo()
Any ideas what is causing the error? What are we missing on our code to copy line items?
Many thanks,
Marc Romagosa
Message was edited by: Marc Romagosa de Riba

We managed to create a line item at VALIDATE script, but not at POST_CREATE. Either it is a bug or it is not possible at POST_CREATE script.

BAPI FOR Deleting a Schedule Line Item from EKES and EKET tables

Dear All,
I would like to for deleting one of the line item from EKES (Po Confirmation ) and the respective line item from the EKET(PO Schedule Line Item Table).
Assume that am allowing the user to select the lineitem from zprogram screen and collecting the PO and Its LIne Item details in an internal table.
Can i Use
<b>BAPI_PO_Change</b> , if so , can anybody tell me the steps to follow to use this bapi for deleting the PO lineItems, since i m going to try BAPI for First time.
pls help me out
Message was edited by: Raja K.P

Hi raja ,
loop at iekko1.
    w_index = sy-tabix.
    item-po_item   = itemx-po_item   = iekko1-ebelp.
    item-quantity = iekko1-mng01.
    itemx-quantity = iekko1-mng01.
    if iekko1-wamng = iekko1-wemng.
    itemx-no_more_gr = item-no_more_gr = 'X'.
    else.
    itemx-no_more_gr = item-no_more_gr = ''.
    endif.
    append item.
    append itemx.
      clear return[].
      call function 'BAPI_PO_CHANGE'
           exporting
                purchaseorder = iekko1-ebeln
           tables
                return        = return
                poitem        = item
                poitemx       = itemx.
      if return[] is initial.
      commit work and wait.
      call function 'DEQUEUE_ALL'.
search for deletion fields which u have to mark 'X'.
before calling this BAPi u have to lock the PO by using ENQUEUE.
<b>
FU BAPI_PO_CHANGE
Text
Change purchase order
Functionality
Function module BAPI_PO_CHANGE enables you to change purchase orders. The Change method uses the technology behind the online transaction ME22N.
Alternatively, the IDoc type PORDCH1 is available. The data from this IDoc populates the interface parameters of the function module BAPI_PO_CHANGE.
Functionality in Detail
Authorization
When you create (activity 02) an Enjoy purchase order, the following authorization objects are checked:
M_BEST_BSA (document type in PO)
M_BEST_EKG (purchasing group in PO)
M_BEST_EKO (purchasing organization in PO)
M_BEST_WRK (plant in PO)
Controlling adoption of field values via X bar
For most tables, you can use your own parameters in the associated X bar (e.g. PoItemX) to determine whether fields are to be set initial, values inserted via the interface, or default values adopted from Customizing or master records, etc. (for example, it is not mandatory to adopt the material group from an underlying requisition - you can change it with the BAPI).
Transfer
Purchase order number
The PurchaseOrder field uniquely identifies a purchase order. This field must be populated in order to carry out the Change method.
Header data
The header data of the Enjoy purchase order is transferred in table PoHeader.
Item data
The item data of the Enjoy purchase order is stored in the tables PoItem (general item data). Changes regarding quantity and delivery date are to be made in the table PoSchedule.
Use the table PoAccount to change the account assignment information.
Services and limits
Changes to existing items cannot be carried out with the Change method. It is only possible to create new items.
Conditions
Conditions are transferred in the table PoCond; header conditions in the table PoCondHeader. A new price determination process can be initiated via the parameter CALCTYPE in the table PoItem.
Vendor and delivery address
The vendor address in the table PoAddrVendor and the delivery address in the table PoAddrDelivery can only be replaced by another address number that already exists in the system (table ADRC). Changes to address details can only be made using the method BAPI_ADDRESSORG_CHANGE.
Partner roles
You can change all partners except the partner role "vendor" via the table PoPartner.
Export/import data
Export/import data can be specified per item in the table PoExpImpItem. Foreign trade data can only be transferred as default data for new items. Changes to the export/import data of existing items are not possible.
Texts
Header and item texts can be transferred in the tables PoTextHeader and PoTextItem. Texts for services are imported in the table PoServicesText. Texts can only be replaced completely.
Version Management
You can make use of the Version Management facility via the table AllVersions.
Return
If the PO was changed successfully, the header and item tables are populated with the information from the PO.
Return messages
Messages are returned in the parameter Return. This also contains information as to whether interface data has been wrongly or probably wrongly (heuristical interface check) populated. If a PO has been successfully created, the PO number is also placed in the return table with the appropriate message.
Restrictions
With this function module, it is not possible to:
Create subcontracting components (you can only use existing ones)
Create configurations (you can only use existing ones)
Change message records (table NAST) and additional message data (this data can only be determined via the message determination facility (Customizing))
Attach documents to the purchase order
Change foreign trade data
Change service data
Change or reexplode BOMs
A firewall prevents the manipulation of data that is not changeable in Purchasing according to the business logic of the purchase order (e.g. PO number, vendor, etc.).
PO items with an invoicing plan cannot be created or changed using the BAPIs
In this connection, please refer to current information in Note 197958.
To change addresses with numbers from Business Address Services (cantral address management), please use the function module BAPI_ADDRESSORG_CHANGE.
To change variant configurations, please use the function module BAPI_UI_CHANGE. More information is available in the BAPI Explorer under the Logistics General node.
In the case of changes that are to be made via the BAPI_PO_CHANGE, a firewall first checks whether the relevant fields are changeable. This approach follows that of the online transaction. Here it is not possible to change the vendor or the document type, for example.
Example
Example of changes made to a purchase order with:
1. Change in header data
2. Change in item
3. Change in delivery schedule
4. Change in account assignment
5. Change in conditions
6. Change in partners
Parameter: PURCHASEORDER 4500049596
Parameter: POHEADER
PMNTTRMS = 0002
PUR_GROUP = 002
Parameter: POHEADERX
PMNTTRMS = X
PUR_GROUP = X
Parameter: POITEM
PO_ITEM = 00001
CONF_CTRL = 0001
Parameter: POITEMX
PO_ITEM = 00001
PO_ITEMX = X
CONF_CTRL = X
Parameter: POSCHEDULE
PO_ITEM = 00001
SCHED_LINE = 0001
QUANTITY = 10.000
PO_ITEM = 00001
SCHED_LINE = 0003
DELETE_IND = X
Parameter: POSCHEDULEX
PO_ITEM = 00001
SCHED_LINE = 0001
PO_ITEMX = X
SCHED_LINEX = X
QUANTITY = X
PO_ITEM = 00001
SCHED_LINE = 0003
PO_ITEMX = X
SCHED_LINEX = X
DELETE_IND = X
Parameter: POACCOUNT
PO_ITEM = 00001
SERIAL_NO = 01
GL_ACCOUNT = 0000400020
Parameter: POACCOUNTX
PO_ITEM = 00001
SERIAL_NO = 01
PO_ITEMX = X
SERIAL_NOX = X
GL_ACCOUNT = X
Parameter: POCOND
ITM_NUMBER = 000001
COND_TYPE = RA02
COND_VALUE = 2.110000000
CURRENCY = %
CHANGE_ID = U
Parameter: POCONDX
ITM_NUMBER = 000001
COND_ST_NO = 001
ITM_NUMBERX = X
COND_ST_NOX = X
COND_TYPE = X
COND_VALUE = X
CURRENCY = X
CHANGE_ID = X
Parameter: POPARTNER
PARTNERDESC = GS
LANGU = EN
BUSPARTNO = 0000001000
Help in the Case of Problems
1. Note 197958 lists answers to frequently asked questions (FAQs). (Note 499626 contains answers to FAQs relating to External Services Management.)
2. If you have detected an error in the function of a BAPI, kindly create a reproducible example in the test data directory in the Function Builder (transaction code SE37). Note 375886 tells you how to do this.
3. If the problem persists, please create a Customer Problem Message for the componente MM-PUR-PO-BAPI, and document the reproducible example where necessary.
Customer Enhancements
The following user exits (function modules) are available for the BAPI BAPI_PO_CREATE1:
EXIT_SAPL2012_001 (at start of BAPI)
EXIT_SAPL2012_003 (at end of BAPI)
The following user exits (function modules) are available for the BAPI BAPI BAPI_PO_CHANGE:
EXIT_SAPL2012_002 (at start of BAPI)
EXIT_SAPL2012_004 (at end of BAPI)
These exits belong to the enhancement SAPL2012 (see also transaction codes SMOD and CMOD).
There is also the option of populating customer-specific fields for header, item, or account assignment data via the parameter EXTENSIONIN.
Further Information
1. Note 197958 contains up-to-date information on the purchase order BAPIs.
2. If you test the BAPIs BAPI_PO_CREATE1 or BAPI_PO_CHANGE in the Function Builder (transaction code SE37), no database updates will be carried out. If you need this function, please take a look at Note 420646.
3. The BAPI BAPI_PO_GETDETAIL serves to read the details of a purchase order. The BAPI cannot read all details (e.g. conditions). However, you can use the BAPI BAPI_PO_CHANGE for this purpose if only the document number is populated and the initiator has change authorizations for purchase orders.
4. Frequently used BAPIs for purchase orders are BAPI_PO_CREATE, BAPI_PO_CREATE1, BAPI_PO_CHANGE, BAPI_PO_GETDETAIL, BAPI_PO_GETITEMS, BAPI_PO_GETITEMSREL, and BAPI_PO_GETRELINFO.
5. For more information on purchase orders, refer to the SAP library (under MM Purchasing -> Purchase Orders) or the Help for the Enjoy Purchase Order, or choose the path Tools -> ABAP Workbench -> Overview -> BAPI Explorer from the SAP menu.
Parameters
PURCHASEORDER
POHEADER
POHEADERX
POADDRVENDOR
TESTRUN
MEMORY_UNCOMPLETE
MEMORY_COMPLETE
POEXPIMPHEADER
POEXPIMPHEADERX
VERSIONS
NO_MESSAGING
NO_MESSAGE_REQ
NO_AUTHORITY
NO_PRICE_FROM_PO
EXPHEADER
EXPPOEXPIMPHEADER
RETURN
POITEM
POITEMX
POADDRDELIVERY
POSCHEDULE
POSCHEDULEX
POACCOUNT
POACCOUNTPROFITSEGMENT
POACCOUNTX
POCONDHEADER
POCONDHEADERX
POCOND
POCONDX
POLIMITS
POCONTRACTLIMITS
POSERVICES
POSRVACCESSVALUES
POSERVICESTEXT
EXTENSIONIN
EXTENSIONOUT
POEXPIMPITEM
POEXPIMPITEMX
POTEXTHEADER
POTEXTITEM
ALLVERSIONS
POPARTNER
Exceptions
Function Group
2012
</b>
regards
prabhu
Message was edited by: Prabhu Peram

Order of delivery schedule line counter at schedule agreements from MRP run

Currently we are using schedule agreements for our long term external suppliers, but we are facing a problem with the order of new delivery schedule lines created during MRP run.
Because of master data settings like, lot size, rounding value, plan delivery time and planning time fence to set as firm new requirements, multiple schedule lines are created with no order for schedule line counter.
Does anyone is aware of a BADI, user exit or customizing control to have this schedule line counter in order?
Thank you
Daniel Guillen
IT
Skyworks Inc.

Hi,
Pls put this query in SD fourms and get immly help because this is technical fourms.
Anil

Automatic Delivery schedule line proposal on scheduling agreements

Hi Experts,
I have a requirements where client wants to have automatic schedule lines in outline agreement i.e. scheduling agreements.
Is there any standard functionality available for configuring this type functionality or we have to customize?
If standard functionality available please suggest which document type we have to use, and what are all the other settings we have to make to work this functionality.
Thanks
Nath

Dear Jagnnath,
The best solution is to create a source list. You can create source list directly from the outline agreemnt main screen (Menu Bar -> Environment) or else use t code ME01. In source list maintain the validity, Pur Org, outline agreement , MRP=2. Here you may set the check box 'FIX', by doing this always scheduling lines will generate with this vendor if there is any requirement of that material.
Hope this may help you.
Vaibhav Mishra

Schedule lines tranfer from R/3 to SUS in a MM-SUS scenario

Hi SRM gurus,
We are working on the MM-SUS scenario where the scheduling agreement is created in the backend R/3 system. Delivery schedule lines are generated in the backend and transfered to the SUS thru. ME9E transaction for sending the delivery schedule to the SUS.
We have a confirmation control key which guides us in SUS to create an ASN in the backend.
Though there is a confirmation control key exist in the SA for that particular line item, when the ASN is sent from SUS to XI to R/3. There is an idoc error in the R/3 which says that there is no confirmation control key though it is there for the line item which is transfered to SUS.
Now Pls. answer my questions :
1) Will ME9E transfer the total lines in the SA or the schedule lines with the delivery schedules only ?
2) Is it possible to resend the same schedule line ( with the updated delivery schedule) to the SUS as per the standard scenario?
3) In the SUS how do we findout the materials corresponding to that particular delivery schedule line. Because in SUS the reference is only the scheduling agreement number as we could not see any scheduline line item.
Pls. suggest.
We are working on SRM(SUS) 5.0 with ECC6.0 as the backend.
Best regards,
Sridhar.

i have seen the code --> where the FM is called for creation of SAR in SRM.
that is FM
BBP_SAPXML1_SUSPO_CREATE_IN --> in this --> search for this
Call API
      IF ls_header-description EQ 'DELINS'.
        CALL FUNCTION 'BBP_API_SUSPO_CRT'
        EXPORTING
          is_header   = ls_header
          it_item     = lt_item
          it_attach   = lt_attach
          it_partner = lt_partner
          it_longtext = lt_longtext
          it_tax      = lt_tax
          it_limit    = lt_limit
          it_sdln     = lt_sdln
        IMPORTING
          es_header   = ls_header_e
this one creates ---> the SAR in SRM.
and also i have seen further --> there is no place where any BADI is also called.
i am afraid it is not possible to control what you want using BADI.
only --> difference between --> New document and the old document is
the Indicator --> C for create
U for update.
And Also if you can see the XML message for the updated document --> you can see all the lines in the XML message.
Not the added lines...

*MRP unable to create Delivery Schedule Lines in MM Scheduling Agreement*

Hi Experts,
I need your help...
The issue is, in-spit of maintaining Source List with an u201CScheduling Agreement with item No.u201D & u201CSource List Usage in MRPu201D as 2 (Record relevant to MRP. Sched. lines generated automatically), MRP run does not generate Schedule Lines, instead PRs are created.
Please help me to understand such behavior and fix the issue as the requirement is to generate Schedule Lines only.
Thanks,
Pratap

Hello
Please check
1) Source List maintained properly in terms of Material # ; plant # ; proper POrg ; Schd Agr # and line item# ; proper validity date & MRP relevant indicator
2) Please also check Quata arrangement if you are using. whether % is maintained correctly against the vendor
3) MD03 , Delivery schedules- should be 3
4) check your planning horizon whether it is NETCH or not
5) check material master -MRP2 view, Procurement type is F- external procurement, schedule margin key if you are using
if everything above is set, then I feel it should work
Also please verify-
lot size, safety stock and the corresponding prod volume for MRP input v/s the stock available in MMBE
example.
MD04, we can see the open del lines.
if SS = 50 , prod volume is 150
1) if MMBE shows 200 then it wont generate any schedule.
2) if MMBE is 180 and your lotsize is 40, then after MD03, you will have a schedule line of 40 (provided if everything is set properly)
Please ensure there are NO open delivery lines . if you find such in MD04, then please close open delivery lines
in calculation of MRP, system considers such open delivery lines are going to receive and no additional schedule line generated even after MRP run
thanks

Automatic schedule lines creation from PR

Hi,
We have a scheduling agreement for certain material
We have maintained a Automatic PO tick in Material master as well as in vendor master
We have also maintained purchasing info fo records and source list
Now we have created a manual PR.
And when we are running the T code ME59 system is creating the PO.
Is it possible to generate schedule lines (automatically through ME59) against a scheduling agreement instead of creating a new PO?
Regards,

Hello,
The transaction ME59 does not select the purchase requisitions assigned to a scheduling agreement. The reason for this is that the Scheduling agreement itself is equivalent to a purchase order. For a purchase requisition assigned to a scheduling agreement, you have to create a delivery schedule only and not a purchase order. Automatic conversion program currently does not handle creation of delivery schedules.
Please use ME58 instead.
br,Gabor

Schedule line different from days accepted by customer calendar

Hi,
When trying to create order for a customer using fcustomer calendar (receiving days = monday), and proposing delivery date for example on a wednesday, it compares a warning messagge that says that next possible goods receving date is the subsequent monday.
If you ignore it, the date in the schedule line remains unchanged (programmed delivery on wednesday).
System uses APO,in the case it runs instead it proposes the nearest monday to the requested date, and no problem with that.
The problem remains on those cases where APO doesn't run.
Any ideas on how to make automatic acquisition of the proposed date of the warning messagge and insert it in schedule line?
User-exit is necessary?
Thanks,
Giuseppe

Anybody that can help me????

Schedule Line info from SD_ORDER_CREATE_WWW

We use the SD_ORDER_CREATE_WWW to simulate an order before creating it. However, this is not returning the schedule lines infomration. For the same material and quantity if I try to create an order in VA01 it gives me multiple schedule lines but when I use the the WWW or BAPI_SALESORDER_CREATEFROMDAT1 I am not getting any schedule lines. I see SAP notes about fixing this issue in earlier versions and I see the correct code so I know it should work . Any ideas on how to get this working ?
Thanks,
Anu

Anybody that can help me????

Customer purchase order number at schedule line level in scheduling agreeme

Hi,
We have one typical requirement from scheduling agreement functionality. The scenario is we receive the schedule lines from Idocs from customer with purchase order number for each schedule line. We need to print that PO number on packing slip and ASN. How do we capture the schedule line po number in SAP SA?
Please share your ideas on this.
Regards, Lakshmikanth

Hi Chandrasekhar,
Thanks for your reply, here we create one delivery for each schedule line quantity, we need to copy the respective purchase order number into delivery. There is no Corelation between schedule line number and additional data field, so we can not use very freely. Do we have any other option?
Regards, Lakshmikanth

Schedule Lines deletion from Scheduling agreement

Similar Messages

Maybe you are looking for