102 combines all the GR qty for the same part # line item in the PO

I had a question on the behavior of movement 102 in SAP
In earlier versions, SAP combines all the GR qty for the same part # line item in the PO both in MIGO & in MB01.
Is a change in functionality in ECC which combines all the qty or is there any config that we are missing?

Hi,
Check your PO item details....is there GR based IV active in your current PO? I know, it should have effect on LIV only but, still trying to see a possibility if it has any impact on GR reversals too....
Regards
Message was edited by:
Gopala Turaga

Similar Messages

Purchase Order summary for a same PO line items

Dear All,
I'm working with SAP script for purchase order. Now problem is that when I give the print from purchase order the data contains several same PO line items, which I don't want printing, but I want summation of their quantities and print them only once.
I have assigned the print program (SAPFM06P) and my own SAP script form to the required (NEU) output type.
Please help.
Regards,
Frenky

Hi
What does "same PO line items" mean?
That mean several equal PO line items with the same: material, description, price and delivery date, but with different order quantity.
I want to summarize all that equal PO line items depending on order quantity and print that total.
Example for this problem is below.
Best regards,
Frenky
Item    Material     Description
               Net value                       Price               Order qty.   Unit                Delivery date
10        646646      HOOD IDG915E/ELICA
                3.644,10                       364,41                10,000      PC                  13.01.2006
20        646646      HOOD IDG915E/ELICA
                5.466,15                       364,41                15,000      PC                  13.01.2006
                                               Total Order qty.:      25,000      PC
30         ..
Total net value:        10.330,65   EUR

Youtube videos choosing main audiotrack, how do I combine all the tracks in Imovie on Mac?

Exactly what the title says. On iMovie, how do I combine all the audio tracks so that Youtube chooses all of them?

This forum is for mobile iMovie.
As far as I've experienced iMovie iOS only exports stereo sound.
you may need the iMovie Mac forum:
https://discussions.apple.com/community/ilife/imovie

Delivery Qty Zero for STO with 2 line item

Hi Guys,
I have a problem when create delivery for STO with 2 line item which contain material with BOM. I have create delivery with tcode VL10G refer to Purchase Order and Delivery successfully created, but delivery qty was zero or empty. I try to fill the dlv qty same with STO Qty but popup message "Only 0 PC for the material available", I have check the stock and there is a stock exist for the material.
I need help for this problem.
Regards
Gunawan

Hi,
Please check if inbound delivery is already created for that Qty
Thanks
Diwakar

Partial goods receipt for PO with multiple line items

Hello All,
While doing MIGO, for a PO with multiple line items, if one line item is having error, will we be able to go ahead with goods receipt? Or entire material document is blocked for doing MIGO?
We will be doing a development - in case if there is problem in goods receipt (checking of any parameter, and if it is missing - we will be posting error message)...is it possible to ahead with next line item and still post the material document?
If partial goods receipt if possible for PO with multiple line items, how do we do it?
Regards,
RJS

Hi
While doing MIGO, for a PO with multiple line items, if one line item is having error, will we be able to go ahead with goods receipt? Or entire material document is blocked for doing MIGO?
No. You cannot post the MIGO, if even one of the PO line item is having problem or giving error.
We will be doing a development - in case if there is problem in goods receipt (checking of any parameter, and if it is missing - we will be posting error message)...is it possible to ahead with next line item and still post the material document?
If you skip a line irem and do GR with next line item, how will you match quantity & value with the vendor Invoice at LIV ?
If partial goods receipt if possible for PO with multiple line items, how do we do it?
Partial goods receipt is possible for PO line items. That means, if PO has 100 qty for line item 1 then you can do GR for 50 now and 50 later depending on the vendors delivery.
Hope this is what you mean by "Partial Goods Receipt".
Edited by: Arun R on May 10, 2010 2:03 PM

How to Restrict Single Delivery Date for PO with Multiple Line Items

Dear Experts,
How to Restrict Single Delivery Date for PO with Multiple Line Items.
System needs to through Error Message if User Inputs Different Delivery Dates for PO with Multiple Line Items in ME21N Tcode.
Can we achive this by Some Enhancement in SAP or Not ???
If so how to do it.
Any Inputs is highly appreciated.
Thanks and Regards,
Selvakumar. M

Hi Selvakumar,
we can resrict the PO to have a single delivery date in all the line items by means of giving a error message or overwiting the delivery date keyed/determined in the line item.
You can use the BADI -> ME_PROCESS_PO_CUST. In which you need to implement the method PROCESS_SCHEDULE.
(for technical aid - This method will be called for each and every PO line item, From the imporing parameter im_schedule we can get all the details of current PO line, even we can change the data in the current PO line. )
Regards,
Madhu.

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.

Field Char(255) for texts in accounting line item

Hi Experts,
I need a field with type/len char(255) for texts in accounting line item.
I know I can use Long Text (EENO_DYNP-ZEILE) but it is not shown in TCode FAGLL03 and that is my need.
Please help me.
Best regards,
Itajaci Júnior

Hi Paul,
Thanks for your reply.
I already have these fields active, but unfortunately the sum of their sizes is not enough. Also, I would have to split the text into four fields and I think that it is not the best option for the customer.
One more time, thanks for your answer.
Any other ideas? It can be a Z field. The most important is that it be shown in Tcode FAGLL03.
Regards,
Itajaci Júnior

Different Line item in invoice for same po line item?

Hi,
Can I post two invoice line item for same po line item?
What is significance in business point view?
Thanks and Regards
Anil Patil

HI,
You can post two invoice for one line item in PO,
Say u raise a PO for 100 and then do a GR for 50 1st and then 50 2nd then you have two invoice for the same PO with same line item.
This can also be done with respect to the delivery number also. and then make a invoice with respect to delievry note in MIRO.
Thanks & regards,
Kiran

Standard report for FI Special Ledger Line Item report

is there any standard report for FI Special Ledger Line Item report

Hi
GD23 for Display of SPL Document
GD13 for Trail Balance of SPL
GCAC for Ledger Comparision
GVTR Balance Carry forward in SPl.
Assign Points if useful.

Problem in CRM_ORDER_MAINTAIN for updating qty in more than 1 line item .

Hi abapers,
I am using BAPI CRM_ORDER_MAINTAIN to update quantity. Its updating the quantity properly if there is single line item for a transaction .If more than 1 line item is there then its throwing an exception* "Document is being distributed - changes are not possible"*.
Scenario:
I have a itab which is having 2 line items for a transaction. i run a loop pass the pass the required parameters in CRM_ORDER_MAINTAIN ,do CRM_ORDER_SAVE , BAPI_TRANSACTION_COMMIT for the 1st line item. When i run the 2nd loop, in CRM_ORDER_MAINTAIN it gives an exception saying NO_CHANGE_ALLOWED for the same transactions 2nd line item. leaving the quantity unchanged for both the line items. What may be the problem?
Note: We cannot say how many line items are there for an transaction. so no chance of grouping all items at a time and saving at a time.
Regards,
Navin

Hi Navin,
Why its not possible to use CRM_ORDER_SAVE only once. I think its possible. Call CRM_ORDER_MAINTAIN in loop for all the line item in transaction and after that call CRM_ORDER_SAVE once. Pls follow the below sample code.
loop at it_item.
call CRM_ORDER_MAINTAIN. (Here append data for all the line items and miantin the transaction).
emdloop.
After endloop call CRM_ORDER_SAVE. Also you can add some wait after CRM_ORDER_SAVE, In order to avoid locking issue.
PLs let me know where you are trying to use CRM_ORDER_MAINATIAN ? In any BADI or Z program ?
Regards,
Amol.

One pr for multiple materials with line items while running mrp

Hi SAP gurus,
              I am config the system for MRP as per my client requerement.
                 We use CBP for different RAW materialsfor example they having a 10 materials for planning,were,
         MRP type is VB,
          LOT size is FX,with Different Reorder points and fix order quantity for all materials,
         My client whant run MRP for all these materials in single time that means they whant multiple item at single levels,
        i soles these requirement with the help of Product Group(sop) and its working but when we running md02 for product group all materials have planed and they give different purchase requistion numbers for all these materials but my client Wants single purchase requistion with line items for all these materials.
     Pls give me the solution for that requirement.
thanks and Regards,
abhi

this is not the way SAPs MRP run works.
Where is the benefit for this?
the requisitions are not even split into header and item table, it is just one table EBAN, and either way you would get exact the same number of records in EBAN.

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

Different ship to party for one of two line items from sales order

Hi Experts,
1. The Sales Order No.19701 is an Export Order, received from M/s. Industries & Construction, Indonesia. We have to supply all the materials on FOB Indian seaport basis.
2. However, we have to dispatch against Line Item No. 280 & 290 to one of our subvendors, M/s.Industries, sec,rabad to complete some Control Assly. as per agreed Inspection terms.
3. After completion of Control Assembly & Client's Inspection materials will be finally dispatched to nearest Seaport for seafreight.
So here i can i map this scenario from sales order to billing, ship to party for those 2 items must be sub vendor.
Thanx in advance
Madhu

Hi madhusudan
You can map different ship to party . First you need to configure customer master for the same.
Add the alternate ship to parties to customer master of sold to party, your export customer.
While creating master data for sub vendors as ship to party ,you need to maintian proper customer pricing pricing procedure and tax classification as you mentioned customer is export customer ,but ship to party seems to be domestic ,so carefully check the same. also check the shipping condition if it is separate for exports.
Then in Sales order transaction on line item data ,change your ship to party for the line item as per the the requirement.
for further processing of this scenario ,like excise invoice and ARE1 u might have lsome issues if ship to party is liable for duties and taxes and Sold to is exempt and you are drawing only one invoice for these 2 separate deliveries. pl check on the same.
I hope this helps
Revert for any queries
Regards
Mandar
Edited by: Mandar Deshpande on Apr 13, 2010 11:04 PM

Need some help on workaround for more than 999 line items in a FI document

Hi all,
user would like to know if there is any way to increase the maximum # of lines for an FI document. Currently, as SAP only allows 999 lines per FI document. The user is encountering an issue when a taxable invoice is uploaded because SAP creates additonal lines for the taxes thereby increasing the line item count beyond the 999 limit. This causes the user to separate out the upload files into several different files which is very time consuming. i have read some replies from previous questions posted on this but none were clear enough on how to actually split the lines and what will happen after the split to the rest of the line items how is the continuation with the first document. can some one give me the explanation or steps on how we can do the split on this document please. we are on 4.6c version. if we have to write some code, what should i explain to the abaper? any kind of inputs would be greatly appreciable.
Thanks in Advance
Jay

Hi,
From your comments, I understand that you are uploading the journals. The steps to handle 999 line items limitation is through functional and technical help.
1. create a dummy GL account
2. In the code, ask the abaper to have a logic such that if more than 900 lineitems (dont check for 999, as some auto postings will be done), then the balance should be loaded to the dummy GL account created and a document should be posted
3. Start reading the remaining docs and follow the same logic as in 2 and ensure that the posting happened in step 2 against dummy GL account should have reversal posting. That is, if step 2 dummy GL account has a credit balance then in step 3 against the same amount a debit entry for the GL account should be posted.
This will ensure that once all the line items are posted, the balance in dummy GL is Zero.
Regards,
Sridevi

102 combines all the GR qty for the same part # line item in the PO

Similar Messages

Maybe you are looking for