Schedule line item data missing in Purchase order form in ECC6.0

Hi All,
We are doing ECC6.0 upgradation project . I am trying to print Purchase order in ECC6.0 , all data is coming fine in PO except schedule line item data is missing.
Same print program and form works fine in 4.7E but schedule line item data missing in ECC6.0.
Print program is a copy of standard SAP program SAPFM06P and layoutset is a copy of MEDRUCK.
If anyone knows if there is any OSS note for the standard print program or any solution please let me know.
Thanks,
Sonali.

Resolved on own.

Similar Messages

I want to pick up Schedule line Delivery date based on Sales Order of Mater

Hi Experts,
I have one scenario like,
I want to pick up Schedule line Delivery date based on Sales Order of Material.
For example :
Go to va03
Give the order no
Press the enter
Double click on material.
Go to Schedule line Tab
Then we can find out the Delivery date .
I want to pick up the that Delivery date. Could you please help on that.
Thanks,
Amjad.

Hi,
schedule line dates are available in VBEP.
VBEP-VBELN = sales order number.
VBEP-EDATU = schedule line date.
REgards,
Raghavendra

Re : schedule line item date change

HI
How to change schedule line item date. Default 5 days inadvance its coming. i want to change that into 8 days.
thanks
mani

Hi,
Please go to t-code VOV8,select your s.doc type and double click it.Pl check no of days in "Requested delivery date/pricing date/PO date" -Lead time in days.
If it is 5,change it to 8.
Schedule line date is also determined after system carry out availability check.
thanks,
vrajesh

Production order line item data

Hello All,
I am working on production orders co03 rite now.
I want to access the line item data for a particular order,
AUFK and AFPO are not giving the details i need,
please advise,
thanks,
Gaurav

Dear Gaurav,
U shud try the Table AUFM to get the details u r looking for.
U will get your required output.
Reward points if u feel it was helpful
Regards
Srinivasan

Alignment Changing in the Purchase Order Form

Hi,
We are using 11i( 11.5.10.2) with oracle 9i database. I am adding one text item in the Standard Purchase Order form.next to the Unit price text item. when i change the canvas.total alignment is changing and also coming blank space in the form when i open in the application.
Can anybody suggest on that issue.
Thanks.

Hi,
I am adding one text item in the Standard Purchase Order formI believe this is not supported -- See (Note: 105127.1 - FAQ (Customization)) for details.
However, if you still want to have this working please verify that you have compile the form successfully after doing the necessary changes.
Thanks,
Hussein

Schedule Line Item 100001 delivery date is missing

Hello Sirs,
After created a sales order in ECC and transferred to TM via XI, the queue remains with STOP status. Entering in transaction /SAPPO/PPO2 I’m facing the error “Schedule Line Item 100001 delivery date is missing”. The delivery date is filled in ECC side.
Is there something that I need to check in TM regarding delivery date?
Thanks.

Please try to edit the PO[Change date] and process it again. This issue happens when we use a conversion program to create PO instead of creating it from UI.

Issue on Purchase order creation with Delivery schedule line items per PR

Hi
Note->Developed inbound FM to create PO's in SAP through IDOC.
We are creating purchase orders from vendor which is coming from Inbound IDOC. Here we are using as BAPI_PO_CREATE1
to create PO's. before that i am passing all the inbound data of the IDOC and getting some Purchase requisions for plant and material wise from EBAN table where we have open PR's and split the inbound line item qauntity as per Open quantity in Purchase requisions. Problem here we are modifing schdule line data as per purcahse requisitions and post the all the shehduline data into above functional module, we are using creation date as delivery date in the scheduling line for each line.
Set1- If we have multiple requisions for each material and plant in the inbound IDOC item , while creating PO using above BAPI
creating PO with delivery date is taken from Purchase requesion date, this only will happend in the first schudle line item always, second line scheulde has taken correctly from creation data as delivery date.
Set2-If we have one requisition for each line item, it will creating correctly for schulding line item as with correct delivery , whcih is not taken from requstion delivery date.
Set 2 is working correctly, but Set1 has problem with delivery date in the scheduling lines particulary for first schduling line item.
Please help me on this issue.
Advance wishes

Hi Satish
Thanks for the reply.
I checked the parameters and it is creating 2 PO when the Indicator Ordering address is set.If I uncheck this Indicator then only one PO is created.
But now my question is from where is the Ordering address taken because for both line items Vendor is same and ordering address is also same.
Then why the system is creating new PO?
Regards
Vaibhav Mahajan

Line item data is not saving while creating a Sales order using Interactive

Hi all,
I am creating a sales order Using Interactive forms. In the form i am having Header data and line item data.I had created two structures one for Header data and one for Line item data. For entering the LINE ITEM DATA i had created a Dynamic table with Buttons ADD ROW and DELETE ROW.
User will Add the Row or Delete the Row based on the requirement.
My issue is When ever the user clicks the SUBMIT button after entering the header data and 3 line items data , Sales order has been created with only first line item and the remaining two line items are not created.
My Interactive form is like below
HEADER DATA
DOC_TYPE
SALES_ORG
DIST_CHN
DIVISION
PURCH_NO
PARTN_ROLE
PART_NO
LINE ITEM DATA
                         ITEM_NO      MATERIAL          PLANT          QTY        COND_TYPE            COND_VALUE
ADD ROW
DELETE ROW
                                                                                SUBMIT
My code for the method ONACTIONCLICK is like below
method ONACTIONCLICK .
data:
      Node_Adobe       type ref to If_Wd_Context_Node,
      Node_Zsaleheader       type ref to If_Wd_Context_Node,
      Elem_Zsaleheader       type ref to If_Wd_Context_Element,
      Stru_Zsaleheader       type If_Main=>Element_Zsaleheader,
      Node_Zsaleitem       type ref to If_Wd_Context_Node,
      Elem_Zsaleitem       type ref to If_Wd_Context_Element,
      Stru_Zsaleitem       type If_Main=>Element_Zsaleitem.
data: header_data type BAPISDHEAD.
data: item_wa type BAPIITEMIN.
data: item_data type table of BAPIITEMIN.
data: partner_wa type BAPIPARTNR.
data: partner_data type table of BAPIPARTNR.
data: sales_order type BAPIVBELN-VBELN.
data: Errorlog type BAPIRETURN1.
navigate from <CONTEXT> to <ADOBE> via lead selection
Node_Adobe = wd_Context->get_Child_Node( Name = IF_MAIN=>wdctx_Adobe ).
navigate from <ADOBE> to <Zsaleheader> via lead selection
Node_Zsaleheader = Node_Adobe->get_Child_Node( Name = IF_MAIN=>wdctx_Zsaleheader ).
Node_Zsaleitem = Node_Adobe->get_Child_Node( Name = IF_MAIN=>wdctx_Zsaleitem ).
get element via lead selection
Elem_Zsaleheader = Node_Zsaleheader->get_Element( ).
Elem_Zsaleitem = Node_Zsaleitem->get_Element( ).
get all declared attributes
Elem_Zsaleheader->get_Static_Attributes(
    importing
      Static_Attributes = Stru_Zsaleheader ).
header_data-DOC_TYPE = Stru_Zsaleheader-DOC_TYPE.
header_data-SALES_ORG = Stru_Zsaleheader-SALES_ORG.
header_data-DISTR_CHAN   = Stru_Zsaleheader-DISTR_CHAN.
header_data-DIVISION = Stru_Zsaleheader-DIVISION.
header_data-PURCH_NO = Stru_Zsaleheader-PURCH_NO.
partner_wa-PARTN_ROLE   = Stru_Zsaleheader-PARTN_ROLE.
partner_wa-PARTN_NUMB = Stru_Zsaleheader-PARTN_NUMB.
   append partner_wa to partner_data.
    Elem_Zsaleitem->get_Static_Attributes(
    importing
      Static_Attributes = Stru_Zsaleitem ).
item_wa-ITM_NUMBER = Stru_Zsaleitem-ITM_NUMBER.
item_wa-MATERIAL   = Stru_Zsaleitem-MATERIAL.
item_wa-PLANT = Stru_Zsaleitem-PLANT.
item_wa-REQ_QTY = Stru_Zsaleitem-REQ_QTY.
item_wa-COND_TYPE   = Stru_Zsaleitem-COND_TYPE.
item_wa-COND_VALUE = Stru_Zsaleitem-COND_VALUE.
append item_wa to item_data.
CALL FUNCTION 'BAPI_SALESORDER_CREATEFROMDAT1'
EXPORTING
    ORDER_HEADER_IN           = header_data
WITHOUT_COMMIT            = ' '
CONVERT_PARVW_AUART       = ' '
IMPORTING
   SALESDOCUMENT             = sales_order
SOLD_TO_PARTY             =
SHIP_TO_PARTY             =
BILLING_PARTY             =
   RETURN                    = errorlog
TABLES
    ORDER_ITEMS_IN            = item_data
    ORDER_PARTNERS            = partner_data
ORDER_ITEMS_OUT           =
ORDER_CFGS_REF            =
ORDER_CFGS_INST           =
ORDER_CFGS_PART_OF        =
ORDER_CFGS_VALUE          =
ORDER_CCARD               =
ORDER_CFGS_BLOB           =
ORDER_SCHEDULE_EX         =
endmethod.
PLEASE SUGGEST ME IF ANY CODE CHANGE IS REQUIRED
Thanks in advance
Ajay

Hi,
The item data is not read because, the dynamically added rows should also reflect back to the Web Dynpro context. When the user clicks on Add Row, use the Onsubmit event to add a empty line to internal table and then bind it to the context. And if the user removes a row, remove a row from internal table and bind it back to the context.
You may refer this article.
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/802f0ed1-a17a-2c10-7db4-d515a5b047ed
Regards,
Runal

What is table name in SAP R/3 for PM order line item data

Hello,
I am extracting data for PM module and Interested in PM order line item data. Table AUFK is for PM order header master data.
Is there any other table for PM order line item master data?
Thanks,
Ishak

Hi Ishak,
The item table is AUFP.
Thanks.

Billing date at line item level in a sales order

HI!
Can anyone let me know the significance of billing date being present at the line item level in a sales order?
And why does it get changed as per the Requested delivery date if the Prop. Pricing date in the maintanenece of sales doc type is set as 'A'?
Can it be different for different line items?

Hello Asha,
Can anyone let me know the significance of billing date being
present at the line item level in a sales order ???
The comprehensive information is available at SAP technical help(F1) for the "BILLING DATE" field at Sales Order line item level...Before raising these type of questions, i would urge to conduct initiate analysis and then post at SDN forum if you are unable to find out answers...For your quick reference, i have extracted the same description for Billing date from SAP techincal help (F1) and pasted below.
Billing date for billing index and printout
+The date on which the billing is processed and booked for
accounting purposes.+
Use
+You can use the billing date as one of the selection criteria
when you process billing documents collectively.+
Procedure
+If invoice dates are defined for the customer, the system proposes
the billing date from the invoice date calendar. If no invoice dates are
agreed, then the actual goods issue date is formed on the basis of
delivery related billing. In order related billing, the billing date of the
order forms the basis of the billing date.+
+If you are billing services, the system proposes the date of services
rendered. You can change the date manually in the sales document.+
+If you are using a billing plan to bill a project, the system can propose
billing dates for the billing plan on the basis of planned or actual dates
in the corresponding milestone.+
+In a billing plan for a maintenance or rental contract, you can specify rules
by which the system determines billing dates on the basis of other dates in the contract.+
Regards,
Sarthak

How to move the item level details to line item in the Purchase order form

Hello,
I am in SAP SRM7.0 system, my customers requirement is that the item level details like MPN (Manufacturer Part Number) etc.. should be moved to line item field in the Puchase Order.
Can any one give me susggestion on this. This is not the correct forum for this thread but still pls post the link of related threads which may help in this regard.
Regards
Madhan

HI Masa,
THanks a lot for your reponse, in the option given by you i could find it to make visible or required but there is clue on moving the MPN to item field in the line item level. Can you give more input on this.
Regards
Madhan

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

In VA01 In Schedule line Delivery date not getting populated

Hello,
We have developed enhancement for VA01 tcode.
Depending upon the quatity entered for a material it should show one more item as free good.
If quatity is 10 for a line item 10 then it should show item 20 by default same mateerial and quatilty as 1.We have done this it is working fine.
But if we select free good item in our case it is 20 and click on schedule line item buttom all quaitity fields getting populated.but delivery date not getting populated for only free good.for line item 10 it showing properly.
Can any one please suggest what i need to do in order to display delivery date for free good.
Thanks in advance.
Regards.

Thanks for your response.
Actually i have seen technical settings for that field.it is rv45a-etdat.this field has value till MV45AFZZ.seen in debugger.
Looks like it is clearing some where after the above include.Any suggisitions welcome.Thanks again.

Schedule line delivery dates change in VA01

Experts,
User is adding some days for a material in maintenance table and it is like below.
Material Days Plant
2525252 100 ABCD
3636363 150 PQRS
The requirement is --
While creating sales orders or changing sales orders(VA01 or VA02) while adding this material(2525252)in the line item - In schedule line items Delivery date should changed (some thing like get added 100days)
I have added my logic in routine RV03VFZZ. But some materials are not getting changed due to avilability check.
How can i bypass availability check ?
(tried in USEREXIT_MOVE_FIELD_TO_VBEP... but no use).
Thanks,
Priya

Take a look an ATP00001 in SMOD. However, this looks to me as a classic case when we're trying to use ABAP to compensate for poor functional choices or an incorrect business process. I find it hard to believe this cannot be done by other means than such funky ABAP.

Issue with the Posting Date of the Purchase Order.

Hi All,
There are fields in BW like SSL1: Time OK, SSL2: Qty OK, SSL3: Time & Qty Ok, SSL4: Days Late (Routines are written to calculate). These fields will indicate whether the delivery against a GR is OK or not with respect to Time, Quantity and the No. of Days..
But here the issue I am facing is
If there is only1 delivery/ GR against a single item the calculation in BW are correct - i.e. for a particular PO if there is only one delivery the above fields like SSL1: Time Ok, SSL2: Qty OK will show like the delivery is done within the specified time and everything is OK (in case if it is delivered within the allotted time)
But if there are multiple deliveries or multiple GR's posted for one PO item, the calculations are going wrong i.e. even if the delivery is done well within the specified time it is showing the wrong calculations like it is delievered too late. Because in this case the earlier dates are overwritten.
Can anyone throw me some light on how can I go about solving this issue.
I am thinking of declaring the Posting Date as the KeyField of the DSO as of now it is a Data field I also want to know the impact of assigning this as a Keyfield.
Thanks in advance,
Prasapbi

Hi,
As I understand, you have a DSO based on Purchase Order and your key field is PO and its line item. The problem as you stated will always be there if you have multiple deliveries/GRs created for a single line item because the system will overwrite the entries for same key.
Problem with adding Posting date as keyfield will be that then your key will be PO-PO Lineitem-Date. When PO will be created, the Posting date will be blank(correct me here if I am wrong), therefore you will have one entry for same PO-line item combination. One without date and other with date, which again would be incorrect. If my assumption about Posting date was wrong, even then your data may not be correct because then you may have many entries with same posting date which again would overwrite each other.
If there is any direct link between PO line item and number of deliveries that will get created for them, then you can bring that field in DSO as keyfield. But I don't think there is any such field.
Looking at your report requirement, I would suggest that you make a DSO based on Goods Receipts and then calculate these keyfigures by comparing the dates between GR posting date and PO line item date.
Else you can change the way your datasource works(if its generic one based on function module). Since your main requirement is to check whether the GR posting date has met your SLA or not, you should fetch all the details only when GR is created and make your key field as PO-PO Line item-GR

Schedule line item data missing in Purchase order form in ECC6.0

Similar Messages

Maybe you are looking for