Create PO WITHOUT Line Items

Hi Gurus,
I would like to create empty PO i.e. without any line Items.
Using ME23N it goes into error but still PO can be put on "Hold" and I still get PO Number with just header data.
Doing same via BAPI ;BAPI_PO_CREATE1' it goes into error saying "No line Items present".Is there any chance of "creating an Empty PO" via FM/BAPI?
Please advice asap.
Thanks,
Vikram.

I would like to create empty PO i.e. without any line Items.
Without purchasing what is the need of PO?
if still you need to same than press HOLD and note the PO number than open it via me23n it will open.
Cheers

Similar Messages

Clearing document without line items

Hello,
While doing automatic/manual clearing, clearing doc gets posted with zero line items. We have requirement that documents without any line item can not appear in the legal books.
Apart from validation/substitution, is there any way to avoid this ?

Hello Mauri,
Thanks for your answer.
Problem is not how clearing rules/lines work but is there any solution in SAP to stop a clearing document being created without line items.
For eg - while doing clearing, FX gain/loss line item arises with zero amount in local currency. I know this is standard behaviour & also correct one, but, the requirement is that such zero lines can not appear in the legal books.
Do you have any solution ?
Thanks in Advance.
Regards,
Amol

How to create a new line item automatically in CRMD_ORDER

Hi,
While creating a sales order in CRMD_ORDER, after user enters a line item say 'xxxx' and press 'Enter', we need to create a new line item say 'yyyy' dynamically. Any ways of how to achieve this functionality?
thanks in advance,
amar.s

Hi Amar
You can use structured products:
Step1:COMM_PR01
Open Product xxxx > Relationships > Tab Component > Select Relationship type = STRSET Set > Assing product yyyy
Step2: IMG > CRM > Transactions > Define Item Categories
Open you item category and in Structure scope field select option A Single-Level Explosion of structured products
Step3: IMG > CRM > Transactions > Define Item Category Determination
create new entry
Transaction type =
Item category group = Category group of xxxx product
main item cat = item cat of xxxx product
item cat = item cat of yyyy product
now when you enter product xxxx , product yyyy will be automatically added
Hope it helps
Rupesh

Shopping cart created with one line item with qty 10 . PR need to be creat

Hi gurus
1SC created for ONE LINE ITEM with QTY 10
PR need to be created with 10 LINE ITEMS with Qty 1.
Classic Scanario
Advise .
2.Also please let me know what the batch jobs for delta ( user data or HR data) upload. To upload all user changed data synchonization job
3.Also please let me know what is the batch job for escalation emails for approvals
SD

close not answered

How do i create a new line item (say 20) in reference to line item 10

Hi all,
I am trying to map a scenario where i want to create a new line item with reference to an existing line item. Where do i get this option in SD, and how could i go about it?
Thanks & Regards
Ravi

> In ECC6 if u go to VA01 and enter the SP and SH,
> Press Propose Item Icon, then one window will pop-up
> asking for Sale Document Number, enter the Number and
> select- selection list, there u will get all the
> line item of the Sale Doc. Select and copy Material
Hi i am on SAP 4.7. How could be the same handled here?

Create a new line item in sales order

Hi,
I have to create a new line item in a sales order. The scenario is that if we donot find the desired quantity from a plant. Then we have to go ahead and pick the remaining quantity from another plant and automatically create a new line item.The new plant is picked from a custom table so u need not worry about it.
According to me I will have to use the BAPI for it but one constraint is that while creating a sales order the order number assignment is not done until saved. So what can be done in the case if its a new document.
Kindly let me know if there is any appropriate user exit or if someone has worked on a similar requirement.
thanks
Varun

Hi,
Thanks for your response. I have tried to use these exits already but the problem dat comes here is dat when we try to use the BAPI we donot have any sales document created in the first instance(i.e. while creating an order) so the BAPI returns error and when i tried to populate the itabs in the program directly the new values just wont get processed.
I think like: in case its a new document and we face this scenario I can just terminate the document creation and create a new document using the BAPI with proper plant assignments.But i am doubtful about the stability of this process.
Kindly comment.
Thanks
Varun

Create AP/AR line item report for parked items

Dear all,
Has anyone been able to create a line item report in AP or AR that includes parked items? I have created an aging report using standard 0SAPDUEAN-01 as a base, using report painter. Now the Finance department want to be able to see the numbers of the parked invoices as well but I am not able to find a way to pull these.
Does anyone know if this is actually possible?
many thanks

Hi,
by using of TCODE. FBV3 it is displaying parked documents
based on document type.
K.Satish

Creating new sub line items before a Sales Order is saved (in CRM)

Hi CRM Experts,
I am pretty new to CRM system. I have a scenario.
The actual business scenario behind this is: the customer can only choose a dummy material while placing an order. The customer will not be able to choose what all materials that will make up this order. So he can place an order for a "Pack" with say Qty as 50 units. The business contains some rules based on which the actual materials are mapped to this dummy material.
User creates a SO in CRM system (using txn CRMD_BUS2000115). Assume a dummy material is added as first line item. The system displays it as line item 10. At this stage I need to create sub line items for this high level line item (item 10) based on what all actual materials can fulfill this. I need to do it programmatically. Is there any BAdI that can be used to do this? Also I need some hints on how to go about this? That is how to do it programmatically. For every sub-item material I need to carry a ATP check and only if the stock is available then add it as a sub line item.
Basically what I need is to create sub line items programmatically exactly in the same way as it would have been created manually. The system is configured to put the sub line item numbers automatically. That is, if the high level item is 10, then sub line items will be automatically numbered as 11, 12 so on.
Please feel free to throw me questions if you need more info.
Thanks a lot in advance.
Regards,
Shyam

Hi,
I have a similar kind of a requirement.
I need to add new line items to the order through the program.
Can you please suggest how did you resolve your issue ?
Thanks in advance!

Use FM SD_SALESDOCUMENT_CREATE for creating free goods line items

Dear Experts,
I have created a program for uploading Sales Order details using FM "SD_SALESDOCUMENT_CREATE".
The program successfully creates Sales Orders.
Now the problem is with the materials which is a free goods item.
i.e. if I enter a material say 'XYZ' which has a 20% free goods then if I enter quantity as 10 then it has to create 2 line items where in 1st line item will have 8 as qty. with value and 2nd line item will have 2 as qty with no value.
It successfully happens when I create Sales Order using tcode VA01.
*&      Form CREATE_SALES_ORDER
FORM create_sales_order.
head_flg = 'T'.
LOOP AT t_socreate02 INTO w_socreate02.
    CLEAR : vbeln, spart, bstnk, bstdk,
            w_itemin, w_iteminx, w_partnr.
    MOVE : w_socreate02-vbeln TO vbeln,
           w_socreate02-spart TO spart,
           w_socreate02-bstnk TO bstnk,
           w_socreate02-bstdk TO bstdk.
    AT NEW vbeln.
      CLEAR : w_sdhead, w_sdheadx.
**Transferring Header Details
      MOVE : 'ZODF'   TO w_sdhead-doc_type,   "Default
             'L001'   TO w_sdhead-sales_org, "Default
             '01'     TO w_sdhead-distr_chan, "Default
             spart    TO w_sdhead-division,
             bstdk    TO w_sdhead-purch_date,
             sy-datum TO w_sdhead-req_date_h,
             bstnk    TO w_sdhead-purch_no_c.
      MOVE : 'I' TO w_sdheadx-updateflag,
             'X' TO w_sdheadx-doc_type,
             'X' TO w_sdheadx-sales_org,
             'X' TO w_sdheadx-distr_chan,
             'X' TO w_sdheadx-division,
             'X' TO w_sdheadx-purch_date,
             'X' TO w_sdheadx-req_date_h,
             'X' TO w_sdheadx-purch_no_c.
    ENDAT.
**Transferring Item Details
    MOVE : w_socreate02-posnr TO w_itemin-itm_number,
           w_socreate02-matnr TO w_itemin-material,
           w_socreate02-zmeng TO w_itemin-target_qty.
    APPEND w_itemin TO t_itemin.
    MOVE : w_socreate02-posnr TO w_iteminx-itm_number,
           'I'                TO w_iteminx-updateflag,
           'X'                TO w_iteminx-material,
           'X'                TO w_iteminx-target_qty.
    APPEND w_iteminx TO t_iteminx.
**Transferring Partner Function Details
    CLEAR : w_partnr.
    MOVE : 'AG'                    TO w_partnr-partn_role, "Sold-to-Party
           w_socreate02-sold_party TO w_partnr-partn_numb.
    APPEND w_partnr TO t_partnr.
    CLEAR : w_partnr.
    MOVE : 'WE'                    TO w_partnr-partn_role, "Ship-to-Party
           w_socreate02-ship_party TO w_partnr-partn_numb.
    APPEND w_partnr TO t_partnr.
**Transferring Schedule Line Details
*Schedule Line 1
    CLEAR : w_schedulesin, w_schedulesinx.
    MOVE : w_socreate02-posnr   TO w_schedulesin-itm_number,
           '0001'               TO w_schedulesin-sched_line,
           w_socreate02-edatu01 TO w_schedulesin-req_date,
           w_socreate02-edatu01 TO w_schedulesin-dlv_date,
           w_socreate02-wmeng01 TO w_schedulesin-req_qty.
    APPEND w_schedulesin TO t_schedulesin.
    MOVE : w_socreate02-posnr   TO w_schedulesinx-itm_number,
           '0001'               TO w_schedulesinx-sched_line,
           'I'                  TO w_schedulesinx-updateflag,
           'X'                  TO w_schedulesinx-req_date,
           'X'                  TO w_schedulesinx-dlv_date,
           'X'                  TO w_schedulesinx-req_qty.
    APPEND w_schedulesinx TO t_schedulesinx.
*Schedule Line 2
    IF NOT w_socreate02-wmeng02 IS INITIAL.
      CLEAR : w_schedulesin, w_schedulesinx.
      MOVE : w_socreate02-posnr   TO w_schedulesin-itm_number,
             '0002'               TO w_schedulesin-sched_line,
             w_socreate02-edatu02 TO w_schedulesin-req_date,
             w_socreate02-edatu02 TO w_schedulesin-dlv_date,
             w_socreate02-wmeng02 TO w_schedulesin-req_qty.
      APPEND w_schedulesin TO t_schedulesin.
      MOVE : w_socreate02-posnr   TO w_schedulesinx-itm_number,
             '0002'               TO w_schedulesinx-sched_line,
             'I'                  TO w_schedulesinx-updateflag,
             'X'                  TO w_schedulesinx-req_date,
             'X'                  TO w_schedulesinx-dlv_date,
             'X'                  TO w_schedulesinx-req_qty.
      APPEND w_schedulesinx TO t_schedulesinx.
    ENDIF.
*Schedule Line 3
    IF NOT w_socreate02-wmeng03 IS INITIAL.
      CLEAR : w_schedulesin, w_schedulesinx.
      MOVE : w_socreate02-posnr   TO w_schedulesin-itm_number,
             '0003'               TO w_schedulesin-sched_line,
             w_socreate02-edatu03 TO w_schedulesin-req_date,
             w_socreate02-edatu03 TO w_schedulesin-dlv_date,
             w_socreate02-wmeng03 TO w_schedulesin-req_qty.
      APPEND w_schedulesin TO t_schedulesin.
      MOVE : w_socreate02-posnr   TO w_schedulesinx-itm_number,
             '0003'               TO w_schedulesinx-sched_line,
             'I'                  TO w_schedulesinx-updateflag,
             'X'                  TO w_schedulesinx-req_date,
             'X'                  TO w_schedulesinx-dlv_date,
             'X'                  TO w_schedulesinx-req_qty.
      APPEND w_schedulesinx TO t_schedulesinx.
    ENDIF.
*Schedule Line 4
    IF NOT w_socreate02-wmeng04 IS INITIAL.
      CLEAR : w_schedulesin, w_schedulesinx.
      MOVE : w_socreate02-posnr   TO w_schedulesin-itm_number,
             '0004'               TO w_schedulesin-sched_line,
             w_socreate02-edatu04 TO w_schedulesin-req_date,
             w_socreate02-edatu04 TO w_schedulesin-dlv_date,
             w_socreate02-wmeng04 TO w_schedulesin-req_qty.
      APPEND w_schedulesin TO t_schedulesin.
      MOVE : w_socreate02-posnr   TO w_schedulesinx-itm_number,
             '0004'               TO w_schedulesinx-sched_line,
             'I'                  TO w_schedulesinx-updateflag,
             'X'                  TO w_schedulesinx-req_date,
             'X'                  TO w_schedulesinx-dlv_date,
             'X'                  TO w_schedulesinx-req_qty.
      APPEND w_schedulesinx TO t_schedulesinx.
    ENDIF.
*Schedule Line 5
    IF NOT w_socreate02-wmeng05 IS INITIAL.
      CLEAR : w_schedulesin, w_schedulesinx.
      MOVE : w_socreate02-posnr   TO w_schedulesin-itm_number,
             '0005'               TO w_schedulesin-sched_line,
             w_socreate02-edatu05 TO w_schedulesin-req_date,
             w_socreate02-edatu05 TO w_schedulesin-dlv_date,
             w_socreate02-wmeng05 TO w_schedulesin-req_qty.
      APPEND w_schedulesin TO t_schedulesin.
      MOVE : w_socreate02-posnr   TO w_schedulesinx-itm_number,
             '0005'               TO w_schedulesinx-sched_line,
             'I'                  TO w_schedulesinx-updateflag,
             'X'                  TO w_schedulesinx-req_date,
             'X'                  TO w_schedulesinx-dlv_date,
             'X'                  TO w_schedulesinx-req_qty.
      APPEND w_schedulesinx TO t_schedulesinx.
    ENDIF.
    AT END OF vbeln.
      PERFORM bapi_salesorder.
      CLEAR : t_itemin[], t_iteminx[], t_partnr[],
              t_schedulesin[], t_schedulesinx[],
              sdno, head_flg.
    ENDAT.
ENDLOOP.
ENDFORM.                    " CREATE_SALES_ORDER
*&      Form BAPI_SALESORDER
FORM bapi_salesorder.
CALL FUNCTION 'DIALOG_SET_NO_DIALOG'.
CALL FUNCTION 'SD_SALESDOCUMENT_CREATE'
    EXPORTING
      sales_header_in       = w_sdhead
      sales_header_inx      = w_sdheadx
      testrun               = p_test
      status_buffer_refresh = 'X'
    IMPORTING
      salesdocument_ex      = sdno
    TABLES
      return                = t_return
      sales_items_in        = t_itemin
      sales_items_inx       = t_iteminx
      sales_partners        = t_partnr
      sales_schedules_in    = t_schedulesin
      sales_schedules_inx   = t_schedulesinx.
IF p_test <> 'X'.
    CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'.
ENDIF.
IF head_flg = 'T' AND p_test = 'X'.
    WRITE :/40 '** E X E C U T E D - I N - T E S T - M O D E **' COLOR 2.
ELSEIF head_flg = 'T' AND p_test = ' '.
    WRITE :/40 '** E X E C U T E D - I N - U P D A T E - M O D E **' COLOR 2.
ENDIF.
IF head_flg = 'T'.
    SKIP 1.
    ULINE /2(139).
    WRITE :/2 sy-vline,
            3 'Dummy SalesOrder No.' COLOR 1,
           23 sy-vline,
           24 'Generated SalesOrder No.' COLOR 1,
           48 sy-vline,
           49 'Return Message' COLOR 1,
          140 sy-vline.
    ULINE /2(139).
ENDIF.
IF sdno IS INITIAL.
    DELETE t_return WHERE type <> 'E'.
    IF NOT t_return[] IS INITIAL.
      LOOP AT t_return INTO w_return WHERE type = 'E'.
        WRITE :/2 sy-vline,
                5 w_socreate02-vbeln,
               23 sy-vline,
               28 sdno,
               48 sy-vline,
               49 w_return-message COLOR 6 INVERSE,
              140 sy-vline.
      ENDLOOP.
    ELSE.
      WRITE :/2 sy-vline,
              5 w_socreate02-vbeln,
             23 sy-vline,
             28 sdno,
             48 sy-vline,
             49 'Sales Order can be processed SUCCESSFULLY' COLOR 7 INVERSE,
            140 sy-vline.
    ENDIF.
ELSE.
    WRITE :/2 sy-vline,
            5 w_socreate02-vbeln,
           23 sy-vline,
           28 sdno,
           48 sy-vline,
           49 'Sales Order created SUCCESSFULLY !!' COLOR 5 INVERSE,
          140 sy-vline.
ENDIF.
ULINE /2(139).
ENDFORM.                    " BAPI_SALESORDER

No reply so closed the thread.

Cancel down payment Invoice and accounting document without lines item

Dear masters,
I have a problem with down payment invoice cancel. As you know when doing invoice down payment request, after release to accounting, the accounting doc will have special G/L indicator is F (noted item). And when I cancel this billing down payment and after release to accounting, the accounting doc of cancel invoice will not have any lines item. Now I want to have lines item for cancel down payment, how can I do that? I really appreciate your support!
Regards,
Nguyen Pham.

Dear Nguyen,
As i understand your process you created Downpayment Request from SD.
Then created Downpayment with reference to that request.
Then you generated Billing invoice and released to accounts.
After that you cleared the downpayment with the Billing document.
Now you want to cancel all this.
First cancel the downpayment by FBRA reset and reverse.
Then cancel the billing document.

Two PO's created with 2 line items in SC

Hi Friends,
I have one query, in one of my shopping cart there are two line items. But when this SC is processed, system has created two diffrent POs.
Anyone knows the reason and the the configuration setting for the same.
Thanks,
subhash

Hi Subhash,
Please go through the following link:
Re: 2 purchase orders from a shopping cart
Thanks
Pradeep

Down payment at PO level without line item

Dear All
At the moment when we post down payment request and confirm down payment F-47 and F-48. The system will ask for PO number with line item no.
In practical situation we pay down payment against a PO and not against each line item in PO. e.g. If we have a PO with 20 line item and require 20% down payment according to current standard setup we have to process F-47 for each of these line items which is not desired.
Therefore is it possible to customize the system to post down payment against PO and not at line item level.
It is possible to post F-47 for vendor without referring to PO at all and only refer vendor but we need to refer PO -for reporting and PO status update purposes- just not at line item level.
Any advise?
Regards
Anant

without PO it is not possible to process F-47.
you can not make PO with line items. At least one line item should be maintined

Delivery get created with one line item from sale ord having two line item

I have an issue when delivery is created with reference to a sales order.
The sale order consist of a header with customer group VBKD-KDGRP = '01'. There are two line item for this header with item 10 having customer group '01' and line item '20' having customer group '02'.
When delivery is created with reference to this sale order the delivery contains only one line item corresponding to line item 10 having customer group '01' of the sale order. But I need to have both the line item in the delivery irrespective of difference in customer group.
What makes this split up of delivery? Is there any configuration or user exit that need to be applied in order to adress this.
<REMOVED BY MODERATOR>
Thanks in advance
Ramachandran Babu
Edited by: Alvaro Tejada Galindo on Jun 13, 2008 5:45 PM

Check if there is any copy routine applied in the copy control from order to delivery - transaction VTLA. The routines themselves can be found in transaction VOFM (Data transfer -> Deliveries). LIKP-ZUKRL field contains the split criteria (by the way, check what's in that field on your deliveries).
It's possible that there is something in the current routine that is forcing the delivery split. Otherwise you can probably use similar approach to make it stop splitting.
Hope this helps.

TR created for each line item

hi,
when i post the document in migo using 311 movement type i am getting separate Tr for each line item,but i need single TR all line items , how to solve the issue.
Thanks
Muthuraman.D

hi,
thx for your answers but user mistakenly put into different movement types for each line item so different TR is created...now the problem solved.
thanks
Muthuraman.D

SD-ABAP:Create SO:BAPI_SALESORDER_CREATEFROMDAT2: Line Item Structure Tab

Hi SD-ABAP,
I'm currently creating SO using BAPI_SALESORDER_CREATEFROMDAT2.
I'm populating the following:
IMPORT:   SALESDOCUMENTIN, ORDER_HEADER_IN, ORDER_HEADER_INX
TABLES: ORDER_ITEMS_IN, ORDER_ITEMS_INX,
                ORDER_PARTNERS,
                ORDER_SCHEDULES_IN, ORDER_SCHEDULES_INX,
                ORDER_CONDITIONS_IN, ORDER_CONDITIONS_INX,
                ORDER_TEXT
I have a BOM material A, with subMaterial A1, A2, A3. By creating manually (VA01), this will automatically appear on the the Line Item of the BOM Material > Structure tab. The structure tab will contain the subMaterial A1, A2, A3.
What I need is to automatically populate the SubMaterial in the Structure Tab of the Line Item having a BOM material.
Has anyone encountered this scenario? I'm not sure if I need to populate: ORDER_CFGS_PART_OF?
Thanks.
FYI, already checked some SD-BOM related OSS notes.

Hi Jamie,
              It will not automatically populated in BAPi, but i think an user exit (Standard SAP code) is doing it for you. I will say not to change the program in the BAPI instead of that use MOVE FIELD TO VBAP userexit to solve this issue. This is quite common scenario and lot of posts are available over the net.
Best Regards,
Tapodipta Khan.

Create PO WITHOUT Line Items

Similar Messages

Maybe you are looking for