Error in creating schedule line aggrement through BAPI

Hi All ,
I want to create schedule line aggrement (VA31) by using BAPI / FM .
I am using " SD_SALESDOCUMENT_CREATE" FM .
Here i am getting error in output when i enter shchedle line data in input .
Error is given below .
E V1 434 No schedule line category could be determined during quantity adjustment
Error only come when i want to create new schedule line ....in Changing any schedule line aggrement there is no error .
I am able to create schedule line aggrement manually .
please help .

Use BAPI_SAG_CREATE

Similar Messages

Unable to create Schedule line(Maintain sch.agreement)

Hi experts,
After running MRP i got Planned order for a certain material and for that material procurement type maintained as "Both internal and external" in material master. After completing the process planned order to purchase requisition, i separately created schedule agreement . Now here i am facing one problem that if i create schedule line with reference to purchase requsition i am getting the error Requisition doc. type NB not allowed with doc.type LP.
pls anybody suggest is there any prob made in the above process
Regs,
SR
Edited by: SP Ramesh on Jan 1, 2010 8:22 AM

go to tcode OLME> schedule agreement> select the line of document type LP and then slecte the folled item category and then selce each item category one by one and then click on the second folders link document type and there give source document type NB
cause of the issue is : the source document type NB is not set with LP document type of schedule agreement

How to create shipment cost document through BAPI?

Hi SAP Guru,
My requirement is to create shipment cost document through BAPI.
Is there any standard BAPI to create Shipment cost documents? If any buddy no please help me out.I am in client place i have find out the solution..
Thanks & Regards,
Pankaj Sinha

Hi Pankaj,
See the following link for more help.
IDOC/BAPI for changing Shipment cost number/document
Regards

Create schedule line

Any function module available for creating new schedule line specifying schedule line type along with other schedule line related entries

HI,
you can user FM : ME_CREATE_SCHEDULE_DOC to create schedule line agreements.
Thansks,
Nelson

Auto Email Throgh SAP After Creating Schedule Line Through MRP Run

Hello experts,
is it possible to have email generation when scheduling lines are created through MRP run ? if yes kindly let me know the procedure.
Regards,
Durgesh

Hello Raghavendra,
For same requirement i did what you suggested but Can you please guide us what Business object needs to be used as start event for WF3100020 which we are activating. Because We are not able to activate the standard workflow.
It will be better if you help us with steps.
Thanks in advance.
Regards,
Yuvraj

Schedule line generation through MRP

hi,
Schedule lines are not generated through MRP.
i Have Maintained all settings.standard PR is creating while
running MRP.the SA account assignment category
is Q(Project-make to order). is this is the reason
for Not geneating Schedule lines?
what needs to be done?
regds

Hi,
Did you set the correct MRP indicator in the source list ?

Mass Delete of Schedule Lines generated through changes in prod Schedule

Hi friends,
Kindly provide me the process of mass deleting schedule lines which are created through changes in Production Schedule in the month end.
Regards,
Ask

Hi,
Try T.code Me17
thanks
Rakesh

How to Change Scheduling Agreement Schedule line data thru BAPI ??

Hii
I want to change the shedule line data for a scheduling agreement .
I used BAPI_PO_CHANGE but as this BAPI is used for PO only this gives a
Error Message for Scheduling agreement .
Please suggest me BAPI or FM to update the Scheduling agreement Schedule line.
Regards
Ajitabh Pradhhan

as BAPI_AGREEMENT_MAINTAIN is not available in 4.6c
Please help me out on hwo to maintain Scheduling Agreements .
Regards
Gaurav

After creating new sales order through BAPI, it is not showing in VA03

Hi Experts
I am developing one program to create sales order using FM BAPI_SALESORDER_CREATEFROMDAT2. In output screen it is showing that the new sales order number created with new sales order number. But whenever I want to display the newly created sales order via VA03 it shows an error message SD document 10007547 is not in the database or has been archived but in program output it shows that 10007547 is created. This is in DEV server. Document numbers are generated by the system sequencially, but it is not reflected in database.
I am also attaching my code below.
REPORT z_bapi_salesorder.
DATA : gt_header LIKE bapisdhd1,
       gt_item TYPE TABLE OF bapisditm,
       gt_itemx TYPE TABLE OF bapisditmx,
       gt_partner TYPE TABLE OF bapiparnr,
       gt_return TYPE TABLE OF bapiret2.
DATA : gs_item LIKE LINE OF gt_item,
       gs_itemx LIKE LINE OF gt_itemx,
       gs_partner LIKE LINE OF gt_partner,
       gs_return LIKE LINE OF gt_return.
DATA : v_vbeln TYPE vbeln_va.
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(30) ord_type FOR FIELD p_auart.
PARAMETERS : p_auart TYPE auart OBLIGATORY.
SELECTION-SCREEN END OF LINE.
SELECTION-SCREEN SKIP 1.
SELECTION-SCREEN : BEGIN OF BLOCK b1 WITH FRAME TITLE text-001.
PARAMETERS       : p_vkorg TYPE vkorg OBLIGATORY,
                   p_vtweg TYPE vtweg OBLIGATORY,
                   p_spart TYPE vbak-spart OBLIGATORY,
                   p_sold TYPE kunnr OBLIGATORY,
                   p_ship TYPE kunnr OBLIGATORY,
                   p_matnr TYPE matnr OBLIGATORY,
                   p_menge TYPE kwmeng OBLIGATORY,
                   p_plant TYPE werks_d OBLIGATORY.
SELECTION-SCREEN : END OF BLOCK b1.
INITIALIZATION.
ord_type = 'Order Type'.
START-OF-SELECTION.
*Header information data.
gt_header-doc_type = p_auart.
gt_header-sales_org = p_vkorg.
gt_header-distr_chan = p_vtweg.
gt_header-division = p_spart.
*Partner information data.
gs_partner-partn_role = 'AG'.
gs_partner-partn_numb = p_sold.
APPEND gs_partner TO gt_partner.
CLEAR gs_partner.
gs_partner-partn_role = 'WE'.
gs_partner-partn_numb = p_ship.
APPEND gs_partner TO gt_partner.
CLEAR gs_partner.
*Item data
gs_item-itm_number = '000010'.
gs_itemx-itm_number = 'X'.
gs_item-material = p_matnr.
gs_itemx-material = 'X'.
gs_item-plant = p_plant.
gs_itemx-plant = 'X'.
gs_item-target_qty = p_menge.
gs_itemx-target_qty = 0.
APPEND gs_item TO gt_item.
APPEND gs_itemx TO gt_itemx.
CLEAR : gs_item, gs_itemx.
CALL FUNCTION 'BAPI_SALESORDER_CREATEFROMDAT2'
    EXPORTING
SALESDOCUMENTIN               =
      order_header_in               = gt_header
ORDER_HEADER_INX              =
SENDER                        =
BINARY_RELATIONSHIPTYPE       =
INT_NUMBER_ASSIGNMENT         =
BEHAVE_WHEN_ERROR             =
LOGIC_SWITCH                  =
TESTRUN                       =
CONVERT                       = ' '
   IMPORTING
     salesdocument                = v_vbeln
    TABLES
     return                       = gt_return
     order_items_in               = gt_item
     order_items_inx              = gt_itemx
     order_partners               = gt_partner
ORDER_SCHEDULES_IN            =
ORDER_SCHEDULES_INX           =
ORDER_CONDITIONS_IN           =
ORDER_CONDITIONS_INX          =
ORDER_CFGS_REF                =
ORDER_CFGS_INST               =
ORDER_CFGS_PART_OF            =
ORDER_CFGS_VALUE              =
ORDER_CFGS_BLOB               =
ORDER_CFGS_VK                 =
ORDER_CFGS_REFINST            =
ORDER_CCARD                   =
ORDER_TEXT                    =
ORDER_KEYS                    =
EXTENSIONIN                   =
PARTNERADDRESSES              =
IF v_vbeln <> space.
    COMMIT WORK.
    WRITE :/ 'Document', v_vbeln ,'created'.
    CLEAR : v_vbeln, gt_header.
    REFRESH : gt_partner, gt_item, gt_itemx.
ELSE.
    WRITE :/ 'Error in creating document'.
ENDIF.
Please give the possible solutions for this. What is reason for that update termination.

CALL FUNCTION 'BAPI_SALESORDER_CREATEFROMDAT1'
    EXPORTING
      ORDER_HEADER_IN           = ORDER_HEADER_IN
WITHOUT_COMMIT            = ' '
CONVERT_PARVW_AUART       = ' '
   IMPORTING
     SALESDOCUMENT             = SALESDOCUMENT
SOLD_TO_PARTY             =
SHIP_TO_PARTY             =
BILLING_PARTY             =
     RETURN                    = RETURN
    TABLES
      ORDER_ITEMS_IN            = ORDER_ITEMS_IN
      ORDER_PARTNERS            = ORDER_PARTNERS
ORDER_ITEMS_OUT           =
ORDER_CFGS_REF            =
ORDER_CFGS_INST           =
ORDER_CFGS_PART_OF        =
ORDER_CFGS_VALUE          =
ORDER_CCARD               =
ORDER_CFGS_BLOB           =
     ORDER_SCHEDULE_EX         = ORDER_SCHEDULE_EX
use bapi_transaction_commit.
Regards,
Venkat

Creating Schedule lines in Scheduling agreement using LSMW

Hi,
I want to upload multiple schedule lines in scheduling agreement using LSMW. I have done the recording and maintained multiple lines in input file. However during execution LSMW creates only one line and keeps on ovewritting the same line. Please let me know how can I create multiple schedule lines.
Regards

First you should search for existing standard LSMW migration objects that possibly cover your scenario. These normally take care of complex header / multiple items / multiple subitems relations.
With a recording you can only load flat structures. Sometimes a "create new lines" / "enter first line" / "save transaction" logic can be constructed to load multiple items to a header (or even subitems to an item?) with a recording, but this can be pretty awkward.
Thomas

Help me to guide create schedule lines in MRP

hi
This is my MRP initial screen
Processing key          NETCH               Net change for total horizon
Create purchase req.    1                   Purchase requisitions
Delivery schedules       3                   Schedule lines
Create MRP list           1                   MRP list
Planning mode             3                   Delete and recreate planning data
Scheduling                   1                   Basic
I already Maintain the Source list in ME01 with Vendor & Plant then input the Scheduling agreement number and the MRP as 2.
but i counld,t get schedule lines why
thanks
jai
Edited by: Jai on Sep 30, 2008 12:55 PM
Edited by: Jai on Sep 30, 2008 12:55 PM

hi friends,
once i run the MRP MD03 it creates only PR
there is no schedule lines
thats also my problem
please expalin and solve my problem
thanks
jai

Error whil creating Service Line item in ME51N using BAPI_PR_CREATE

Hi Experts,
            Am able to create PR number using BAPI_PR_CREATE, but when am trying to create Service line item am getting acc assignment error please check my code and solve my issue. ..its very adj please help me .
DATA : t_bapimereqitemimp TYPE TABLE OF bapimereqitemimp ,
      t_bapimereqaccount TYPE TABLE OF bapimereqaccount,
      t_bapimereqaccountx TYPE TABLE OF bapimereqaccountx,
      t_pritemx    TYPE TABLE OF bapimereqitemx,
      wa_bapimereqitemimp        TYPE bapimereqitemimp,
      pr_number TYPE bapimereqheader-preq_no,
      wa_prheader TYPE   bapimereqheader,
      wa_prheaderx TYPE bapimereqheaderx,
      wa_pritemx   TYPE bapimereqitemx,
      wa_bapimereqaccountx TYPE bapimereqaccountx,
      wa_bapimereqaccount TYPE bapimereqaccount,
      t_return     TYPE TABLE OF bapiret2,
      wa_return    TYPE bapiret2.
DATA : t_bapi_srv_limit_data TYPE TABLE OF bapi_srv_limit_data,
        wa_bapi_srv_limit_data TYPE bapi_srv_limit_data.
DATA servicelimitx TYPE TABLE OF bapi_srv_limit_datax.
DATA w_servicelimitx TYPE bapi_srv_limit_datax.
DATA : t_servicelines TYPE TABLE OF bapi_srv_service_line,
        w_servicelines TYPE bapi_srv_service_line,
        t_servicelinesx TYPE TABLE OF bapi_srv_service_linex,
        w_servicelinesx TYPE bapi_srv_service_linex,
        t_bapi_srv_acc_data TYPE TABLE OF bapi_srv_acc_data,
        w_bapi_srv_acc_data TYPE bapi_srv_acc_data,
        t_bapi_srv_acc_datax TYPE TABLE OF bapi_srv_acc_datax,
        w_bapi_srv_acc_datax TYPE bapi_srv_acc_datax.
DATA : t_bapimereqitem TYPE TABLE OF bapimereqitem,
        w_bapimereqitem TYPE bapimereqitem.
DATA : t_bapimereqitemx TYPE TABLE OF bapimereqitemx,
        w_bapimereqitemx TYPE bapimereqitemx.
wa_prheader-pr_type = 'RV'."lv_doc_type.
wa_prheaderx-pr_type = 'X'.
wa_bapimereqitemimp-preq_item = '1'."wa_eban-item.
wa_bapimereqitemimp-pur_group = '100'."wa_eban-ekgrp.
wa_bapimereqitemimp-preq_name = 'E.R. TITTO'."wa_eban-afnam.
wa_bapimereqitemimp-short_text = 'AC Fitting'."wa_eban-txz01.
wa_bapimereqitemimp-material   = ' '."wa_eban-matnr.
wa_bapimereqitemimp-plant      = '1000'."wa_eban-werks.
wa_bapimereqitemimp-store_loc = 'ST00'."wa_eban-lgort.
wa_bapimereqitemimp-matl_group = 'Z13'."wa_eban-matkl.
wa_bapimereqitemimp-quantity   = '1'."wa_eban-menge.
wa_bapimereqitemimp-unit       = 'AU'."wa_eban-meins.
wa_bapimereqitemimp-deliv_date = '20140604'."wa_eban-lfdat.
wa_bapimereqitemimp-preq_price = '100'."wa_eban-preis.
wa_bapimereqitemimp-item_cat   = 'D'."wa_eban-pstyp.
wa_bapimereqitemimp-acctasscat = 'K'."wa_eban-knttp.
wa_bapimereqitemimp-fixed_vend = ' '."wa_eban-flief.
wa_bapimereqitemimp-purch_org = '1000'."wa_eban-ekorg.
wa_bapimereqitemimp-currency   = 'INR'."wa_eban-waers.
wa_bapimereqitemimp-pckg_no = '00000001'.
wa_bapimereqaccount-preq_item = '1'."wa_eban-item.
*wa_bapimereqaccount-serial_no = '01'.
wa_bapimereqaccount-gl_account = '0000002244'."wa_eban-sakto.
wa_bapimereqaccount-costcenter = 'OPSD'."wa_eban-kostl.
APPEND wa_bapimereqitemimp TO t_bapimereqitemimp.
APPEND wa_bapimereqaccount TO t_bapimereqaccount.
wa_pritemx-preq_item = '1'."wa_eban-item.
wa_pritemx-pur_group = 'X'.
wa_pritemx-preq_name = 'X'.
wa_pritemx-short_text = 'X'.
wa_pritemx-material   = 'X'.
wa_pritemx-plant      = 'X'.
wa_pritemx-store_loc = 'X'.
wa_pritemx-matl_group = 'X'.
wa_pritemx-quantity   = 'X'.
wa_pritemx-unit       = 'X'.
wa_pritemx-deliv_date = 'X'.
wa_pritemx-preq_price = 'X'.
wa_pritemx-item_cat   = 'X'.
wa_pritemx-acctasscat = 'X'.
wa_pritemx-fixed_vend = 'X'.
wa_pritemx-purch_org = 'X'.
wa_pritemx-currency   = 'X'.
wa_pritemx-pckg_no   = 'X'.
wa_bapimereqaccountx-preq_item = '1'."wa_eban-item.
*wa_bapimereqaccountx-serial_no = '01'.
wa_bapimereqaccountx-preq_itemx = 'X'.
wa_bapimereqaccountx-serial_nox = 'X'.
wa_bapimereqaccountx-gl_account = 'X'.
wa_bapimereqaccountx-costcenter = 'X'.
APPEND wa_pritemx TO t_pritemx.
APPEND wa_bapimereqaccountx TO t_bapimereqaccountx.
**Service item limit
*wa_bapi_srv_limit_data-doc_item = '10'.
wa_bapi_srv_limit_data-overall_limit = '1000'.
wa_bapi_srv_limit_data-exp_value = '800'.
APPEND wa_bapi_srv_limit_data TO t_bapi_srv_limit_data.
*w_servicelimitx-doc_item = '10'.
w_servicelimitx-overall_limit = 'X'.
w_servicelimitx-exp_value = 'X'.
APPEND w_servicelimitx TO servicelimitx.
w_bapimereqitem-preq_item = '10'.
***w_bapimereqitem-preq_name = 'E.R. TITTO'.
***w_bapimereqitem-plant = '1000'.
***w_bapimereqitem-store_loc = 'ST00'.
***w_bapimereqitem-matl_group = 'Z03'.
***w_bapimereqitem-quantity = '1'.
***w_bapimereqitem-unit = 'AU'.
w_bapimereqitem-item_cat = 'D'.
w_bapimereqitem-deliv_time = '20140604'.
w_bapimereqitem-acctasscat = 'K'.
**w_bapimereqitem-consumpt = 'U'.
APPEND w_bapimereqitem TO t_bapimereqitem.
**w_bapi_srv_acc_data-doc_item = '1'.
**w_bapi_srv_acc_data-outline = '0000000001'.
*w_bapi_srv_acc_data-srv_line = '20'.
w_bapi_srv_acc_data-serial_no = '10'.
w_bapi_srv_acc_data-serial_no_item = 'D'.
*w_bapi_srv_acc_data-quantity = '1'.
*APPEND w_bapi_srv_acc_data TO t_bapi_srv_acc_data.
**w_bapi_srv_acc_datax-doc_item = '1'.
**w_bapi_srv_acc_datax-outline = '0000000001'.
*w_bapi_srv_acc_datax-srv_line = '20'.
**w_bapi_srv_acc_datax-serial_no = '01'.
**w_bapi_srv_acc_datax-serial_no_item = '01'.
*w_bapi_srv_acc_datax-quantity = '1'.
*APPEND w_bapi_srv_acc_datax TO t_bapi_srv_acc_datax.
w_servicelines-service = '00000001'.
APPEND w_servicelines TO t_servicelines.
w_servicelinesx-service = 'X'.
APPEND w_servicelinesx TO t_servicelinesx.
CALL FUNCTION 'BAPI_PR_CREATE'
   EXPORTING
     prheader        = wa_prheader
     prheaderx       = wa_prheaderx
   IMPORTING
     number          = pr_number
   TABLES
     return          = t_return
     pritem          = t_bapimereqitemimp
     pritemx         = t_pritemx
     pritemexp       = t_bapimereqitem
     praccount       = t_bapimereqaccount
     praccountx      = t_bapimereqaccountx
     servicelimit    = t_bapi_srv_limit_data
     servicelimitx   = servicelimitx
     servicelines    = t_servicelines
     servicelinesx   = t_servicelinesx
     serviceaccount = t_bapi_srv_acc_data
     serviceaccountx = t_bapi_srv_acc_datax.

Hi,
Check this Thread , Thread1 . It might help you to resolve the issue.
Thanks
KH

BADI / user-exit for MD02 while creating Schedule Lines

Hi experts,
I have a problem with implementation that I'm designing.
Current situation:
While MRP run (MD02 or background) new Schedule Lines are being created in reference to MM Scheduling Agreement.
Example:
04.08.2014
SchLne
5500000415/00010
200
04.08.2014
IndReq
VSFB
200-
05.08.2014
SchLne
5500000415/00010
300
05.08.2014
IndReq
VSFB
300-
2 Schedule Lines where created - for wuantity 200 and 300.
Target:
There is a need to create more than one Schedule Line per day during MRP run. According to example there should be for example 2 Schedule Lines in 04/08 and 3 Schedule Lines in 05/08 all for quantity = 100. There is possibility to change Schedule Lines in ME38, but there is a need to make a change during creatin while MRP run.
04.08.2014
IndReq
VSFB
200-
04.08.2014
SchLne
5500000415/00010 *
100
04.08.2014
SchLne
5500000415/00010 *
100
05.08.2014
IndReq
VSFB
300-
06.08.2014
SchLne
5500000415/00010 *
100
06.08.2014
SchLne
5500000415/00010 *
100
06.08.2014
SchLne
5500000415/00010 *
100
So instead of creating only 2 Schedule Lines, MRP should create 5.
I'm looking for a BADI/user-exit to edit Schedule Lines which are to be created by MRP and change it tn reference to the needs.
I found only one BADI:
BADI: MD_CHANGE_MRP_DATA
method: CHANGE_MDPSX_MDBS
The priblem is that this method is only being executed when there are Schedule Lines which already exist.
Maybe some of you have done some extension similar to mine? Please give me advice where I should put extension.
Thanks in advance!

Dear Saravaran,
Thanks for the reply.
This will not suits to us. The provided BADI will works upto Posting the material document in transaction MIGO and it will not considered for the FI level entries.
Hope you could have understand mine requirement.
The requirement of mine is:
While doing the GR with ref to PO the material documnet will be posted and subsequently FI documnet will be generated in Background. While generating the FI document i need to manipulate the values for the G/L. So that the manipulated values will be flow into BKPF and BSEG tables.
Thanks.
Regards
Swamy

MRP in third party scenario. System not creating schedule lines

HI
I am using third party subcontracting scenario. As i am purchasing material but i am not taking material in under my company. I am paying to my vendor but the delivery is going to my subcontractor.
Here i am able to create planned order or purchase requisition. But MRP is not generating schedule lines for that vendor.
Regards,
Anand.

Hello,
Check the following settings.
1. Source list active in Material master.
2. Valididy of the source list.
3. Any quota arrangement
4. Purchase infor record.
Note: all are OK, but still PR's only created, then check for the requirement date, if the requirement date lies before the validity of the source list then also system will create only purchase requisitions.
for this calculation you have to check the lead time for procurement cycle you have to check. Based on this no. of days only system will try to create the procurement proposals.
If the lead time is very high and this is going beyond the sourcelist validity, then also PR's only created.
So there are so many possibilities. check for the above said things and revert back.
regards,
<Manick>

Provide -- the steps involve (in detail) to create schedule lines from MRP

Dear All
Please provide me with the steps (in details) involved to create the schedule lines automatically from MRP.
Early help would be appreciated.
Regards
Rahul Bhardwaj

Hi,
1. In Material Master --> Purchasing View --> maintain the Tick for Scource list.
2. Create th Scheduling Agreement. (valid)
3. Maintain the Source list with the Scheduling Agreement and MRP indicator as 2.
4. MRP Control Parameters - Delivery Schedules - 3 (Schedule Lines).
After MRP Run, system will create the Sched. Lines for you..
For your earlier questions also please check these points..
Regards,
Siva

Error in creating schedule line aggrement through BAPI

Similar Messages

Maybe you are looking for