Dummy Purchase order

Dear Experts,
Kindly explain the processes step by step of Dummy Purchase order. Starting with PR, PO, GRN, MIRO.
The difference between Dummy PO & Standard PO
Regards
Pandari

Hi
Dummy Purchase Order is not a SAP functionality but some times used because of the business requirement.
Dummy purchase order is usally used to have the legal document. Its used for pretty Items, where there is no need of GR/Invoice.
In general the Dummy POs are same as Blanket POs that are used for consumable materials that does not need to have Master Record with Item Category ' B' i.e.limit, where in the PO validity period as well as the limits are to be mentioned for the simplicity of procurement.
Regards
Anand

Similar Messages

Frameworder and dummy purchase order.

Hi Friends
what is different between dummy purchase order and frame work purchase order..
Can you give the process of these purchase orders?
Thanks & Regards,
Renuga.A

Hi,
Dummy PO and Blanket PO are same
In general the Blanket POs are used for consumable materials such as Xerox papers with a short text (does not need to have Master Record) with Item Category ' B' i.e.limit, where in the PO validity period as well as the limits are to be mentioned for the simplicity of procurement.
Blanket PO are valid for a longer period of time
Document type is FO
In Frame work PO you have to mention From date and To date (compulsory)

Standard SAP Document Type DB (Dummy Purchase Order)

Hello fellow experts!
I have seen this PO document type at previous clients and was wondering what the intended use is? I know this was not customer-specific because I had seen it at several client sites (using 4.6c and 4.7). It looks like my current client has deleted it from their list of document types so I can't research it myself.
I first asked about it when I was attending SAP's MM Configuration course SCM550 several years ago. This document type was not mentioned in any training materials but was clearly visible in the training system. The instructor asked his colleagues at the end of the day but was never able to provide an answer. I see no reference to it on help.sap.com or by doing a Google search.
Any information would be greatly appreciated. There may be some great functionality I've never known of!
Regards,
Jason

In ECC 6.0 It is blanket PO
Dummy PO and Blanket PO are same
In general the Blanket POs are used for consumable materials such as Xerox papers with a short text (does not need to have Master Record) with Item Category ' B' i.e.limit, where in the PO validity period as well as the limits are to be mentioned for the simplicity of procurement.
In SAP, Blanket Purchase Orders refer to the business process where you have a Purchase Order with a validity period (start / end date) and a limit on the item. No Goods Receipt takes place. Payment is triggered by Invoice.

Dummy purchase order receipt record

hello. i'm running an Oracle 11gR1 database.
I am writing reports against Purchasing Data and want to create a dummy record at the receipt level for any unreceived line items
*Sample Data*
Order No     Line No     Release No    line_qty          Receipt No          Receipt Status     Received Qty
MNG012876-CV     1     1          5          1           Received               2
MNG012876-CV     2     1          5          2           Received               3
MNG012876-CV     2     1          5          null           null              null
*Want Data to look like*
Order No     Line No     Release No     line_qty     Receipt No     Receipt Status     Received Qty
MNG012876-CV     1     1          5          1          Received     2
MNG012876-CV     1     1          5          2          Received     3
MNG012876-CV     2     1          5          0          Unreceived     5                              Sample Data to Use
select 'MNG012876-CV' as Order_No
,1 as line_no
,1 as release_no
,5 as line_qty
,1 as receipt_no
,'Received' as Receipt_Status
,2 as Qty
from dual
union all
select 'MNG012876-CV' as Order_No
,1 as line_no
,1 as release_no
,5 as line_qty
,2 as receipt_no
,'Received' as Receipt_Status
,3 as Qty
from dual
union all
select 'MNG012876-CV' as Order_No
,2 as line_no
,1 as release_no
,5 as line_qty
,null as receipt_no
,null as Receipt_Status
,null as Qty
from dual
Thank you in advance

Maybe NOT TESTED!
select order_no,
       line_no,
       release_no,
       line_qty,
       nvl(receipt_no,0) receipt_no,
       nvl(receipt_status,'Unreceived') receipt_status,
       nvl(received_qty,sum(received_qty) over (partition by order_no
                                                    order by receipt_no nulls last
          ) received_qty
from tRegards
Etbin

Inbound delivery creation with out reference to purchase order

As per my requirement i am third party warehouse who provides space for my customers . i receive goods from lot of customers who have their own ERP system or may not be any ERP system . The goods i am going to receive is non valuated material. How do i receive GR in the above scenario.
I am thinking to create one dummy purchase order and then create inbound delivery. Otherwise How do i create inbound delivery without reference to any documents?.

Hi,
Inbound delivery
You can create purchase Order(ME21N),inbound delivery in t.code: VL31N and Goods Receipt in t.code: VL06IG and post the goods wrt PO into the GR blocked stock (movement 103) and finally you can release goods from blocked stock to unrestricted stock with 105 Movement type, if satisfy quality or other criteriau2019s.
Or
As you said, you just keeping customer stock better create material with non-valuated material type UNBW and do regular process like PO, GR & GI etc.Inbound delivery not required for above said process.
Regards,
Biju K

Purchase Order mandatory for Spl Gl Transactions

Hi Sapiens,
I have a requirement to make the Purchase order field mandatory when we do the Spl Gl Transactions, such as Retention, Advance to Suppliers and but not to the Employee related Spl Gl Transaction.
I have a Option to see:
1. I am trying to make the posting keys 29 and 39, the purchase order field as mandatory.
Problem is that this will apply to all kinds of Spl Gl's. For this want to check that this shud not apply for Empl gl
Option for this is(May be)
Whenever we post the Employee Spl Gl Transactions, I wanted to create a dummy purchase order and assign the same.
Will this work or any kind of complications will arise, please throw some light on this.
OR
Please any one would suggest me for any other solution.
Points are assured. Please help me in resolving this issue.
Thanks and Regards,
Sri

hi sree,
Relating u r queary require entry for Purchases order number in pk 29 and 39 dont made required entery for posting key level.
Create Two Special Gl account two for employee another is service vendor.
make change in Spl Gl account Field status Group level so u can post the transaction smoothly.
Relating to employee Spl Gl Account would be different and field status also.
any clarification let me know.
Thnks and Regards
Laxmi

Purchase order document types

Hi,
What are the different document types available for purchase orders? Could that be checked anywhere in SPRO?
Thanks and regards
Aparna

Dear,
The document type is used for Number range and also in release stregety.
You can create ur Document type for PO.
SPRO --> MM --> Purchasing --> PO --> Define Docuemnt type.
Std PO Doument type are
DB     Dummy Purchase Order
EUB     DFPS, Int. Ord. Type
FO     Framework Order
NB     Standard PO
UB     Stock Transp. Order
there u can assign Number range.
Regards,
Pardeep Malik
Edited by: Pardeep Malik on Mar 27, 2009 8:11 AM

Archiving purchase orders of a specific order-type

hello,
does anyone have a simple-doc or plan for archiving purchase orders. archiving for dummy's as I have never done this?
points to be taken into consideration:
- order of a specific type (ZRL0)
- order must be older then 10 days
thanks,

Hi,
In order to archive PO's , there are a number of considerations that must be taken into account.
The archiving program SARA -> MM_EKKO , Write , does a large number of checks before archiving can be done.
The first step is to go to SARA -> MM_EKKO , customizing. In here , you can specifiy what kind of documents you want to archive and specify the retention period (document life) for each type of document.
For example :
Go to C MM-PUR : Reorganization PO
You will find several type of PO Doc types
DB     Dummy purchase order           Standard
NB     Standard PO           Standard
NB     Standard PO     K     Consignment
NB     Standard PO     L     Subcontracting
NB     Standard PO     S     Third-party
NB     Standard PO     D     Service
UB     Stock transport ord.     U     Stock transfer
Suppose you want to archive Standard PO's , go into the customizing option and then set the residence time 1 and residence time 2.
Res time 1 is the number of days which must elapse after which a deletion indicator can be set for the document. The elapsed days are calculated from the last change date of the document record in EKKO table.
Res time 2 is the number of days which must elapse after which a document with a deletion indicator can be actually deleted out of the EKKO table.
Once the customizing is finished , then you should run the SARA Preprocessing job (which sets the deletion indicators for the selected set of documents) , then the write job (which will write the DLT status documents to an archive file) and then the delete step (which will remove documents from the EKKO and other related Purchasing tables. TO get a trailer of what gets archived and deleted , run the archive write job in "Test" Mode , rather than "Production" mode.
Hope this helps.
-Chandra

Printing Purchase Orders after they have been created using BAPI_PO_CREATE1

Hi
We have a requirement to develop a Z program to to alloow certain users to create and print "special" dummy Purchase Orders (PO).
Using BAPI_PO_CREATE1 I have been able to create the PO no problem. But how on earth do you get them to physically print out ?
BAPI_PO_CREATE1 is meant to be an alternative to ME21N. In ME21N you can create a "PO message" which is actually a print output of the PO) and have it sent to the spool, depending on config. However, you can't use BDC with ME21N.
I expected the BAPI to have some sort of table/structure to pass print parameters that emulated ME21N's PO message, but there is none.
Anybody done this ?
cheers Hugh

Well, if you had your PO output configured to print immediately when the PO is created, then the BAPI call would result in a printout.
But if you don't want to always print a PO when a new document is created, you could set up a new output type for 'print immediately' and then attach a condition in the output configuration that checks if a certain criterion is met (so for instance if the PO was created via the BAPI), and only if this condition is met would the processing continue.
That way, you could keep the current PO output process (on request only), and have a conditional output that'd only be processed for POs created by the BAPI.

Purchasing Accruals on Closed Purchase Orders

I am having an issue with Purchasing accruals being performed on a closed purchase order. The accrual does not appear in the Uninvoiced Transactions Register, but is accrued in the Purchasing journal entry nonetheless. The purchase order is "closed". I am trying to figure out why the amount is being accrued and how to stop the accrual. Anyone have any ideas? Is this a bug or should I try to "Finally Close" the PO?
I also noticed that when this PO accrued in the first month, there were two accrual lines for the purchase order. One had a correct accrual of $67.20 and then there was a second line of $14.70 that was accrued for the PO. The $14.70 is the amount that has been continuing to accrue even though the PO has been "closed".
This is in version 11.5.
Thank you,
Erik

Here are the details of the PO:
Quantity = 1
Qty Rec'd = 1
Qty Billed = 1
Qty Cancelled = 1
Cancelled (flag) = No flag
Hi Erik,
interesting case ! Please note above. You have mentioned "Qty Cancelled = 1", is it a typo?
Assuming that it is a typo error, I don't think finally closing it will solve the problem.
Apart from quantity difference in received vs. billing there may be other cases like incorrect PO or invoice unit price, supplier billing discrepancies (since you have mentioned billing was in installments).
I'll suggest the following checks first before taking any action. Please test in a cloned instance first
- Run "Accrual Reconciliation Report" / "Accrual Rebuild Reconciliation Report" and check what is coming ... do you see the problematic entry
- Check whether there are any other reasons apart from quantity received vs. invoiced mismatch
- Try Accrual Write-Off option in Purchasing to clear that entry (refer PO
- Pass a manual journal entry in GL
For the last 2 steps consult with finance guys.
You can use Accrual Write Off Report as reference for manual journal entry in GL.
Once you are satisfied with the results, apply the solution in production with approval from finance.
Another option could be to use a "dummy" invoice to match the remaining amount.
Please let me know the results.
Good luck!
Thanks
Supro

Reg: IDOC Purchase Order

Hi All,
I have a requirement to trigger a Purchase Order from Stock Transport Order (STO).
So whenever the STO is created, IDOC needs to be triggered & create a auto PO in the same client.
I tried with some examples from forum thread, but all goes in vain.
Could you please advice, what are all the steps needed to achieve this with in a same client. I have created a dummy logical system for Inbound processing with tRFC. Could you please advice this step is really needed.
Thanks & Regards,
Uswin
Edited by: Uswin B on Nov 21, 2011 11:40 AM

1. You need to setup output determination on the STO (transaction NACE, Application EF). You can create output type similar to NEU and assign it to o/p determination procedure linked to your STO document type. You can't use NEU though as it is configured to create ORDERS message type IDoc. To create PO you need message type PORDCR1.
2. You have to write your own function module to output IDoc of message type PORDCR1 and call MASTER_IDOC_DISTRIBUTE to trigger it. It is easy if you only map the minimum required fields so that the IDoc doesn't fail in syntax and take it from there. There are no standard functions that I know that created PORDCR1 message type IDoc (others chip in if you know). You need to create your own outbound process code with ALE processing as medium in the output type.
3. You can set the IDoc from the output type with direct 2 (as inbound) and set up partner profile in the output condition record to point to your inbound LS partner profile
4. You need to assign inbound message type:PORDCR1, IDOC type PORDCR101 and Process code: BAPI to your receiving LS partner profile
Those are the settings you need to do. I can't elaborate as there are many things specific to your implementation

To add Net price in Purchase order

Hi,
I have a sceneria where i need to add net price against line item which was marked as free in purchase order (Net price is 0). Subsequently material was deliverd from vendor and GI also was done. Goods receipt is also completed. This material batch number is consumed for custmer sales orders subsequently. There is 0 quantity available for this material in the plant. Now the user wants to change the net price to 2 for the line item. To change net price in purchase order, we tried to cancel GR material document.But we get an error that 'Deficit of unrestricted use' for the batch number.
Can any one give us solution for changing the net price in purchase order?
Regards,

Hello,
the only chance to add a PO price is to unflag the free flag in ME22N. This is only possible when quantity received for the PO is zero. Therfore you must reverse the quantity received by doing a dummy receipt for the batch, reverse the GR for PO, you change the flag, set a price, redo GR for the PO, reverse the dummy receipt.
Hope this helps, regards
Michael

GTS 7.2 - Error with account assigned purchase order without material

All,
I am creating an account assigned purchase order without any material master in the feeder system (ECC 5.0) and it a standard SAP functionality.
I am getting the following GTS related pop up message and documents are posted to technically incomplete documents in GTS 7.2.
"Legal Control: Custs Prod. Mast. Required
Material "
Any ideas on how get rid of this error message
Edited by: James Puzon on Oct 3, 2008 9:32 PM

James,
Even though material numbers are not mandatory on POs in the feeder system (ie in ECC) they ARE mandatory in SAP-GTS.
This means that every line item (PO, SO, delivery) that is sent to GTS for compliance screening or Customs processing MUST have a material number in the feeder system. You have a couple of options to resolve this:
1. Always use a material number on all transactions that you enter in your feeder system if they are exports or imports (ie relevant for GTS). You can create service materials or "dummy" materials in ECC for items such as user manuals, warranties or installation services that are part of a particular shipment.
2. You can add logic in the interface for GTS to always transfer a particular material number to GTS if the material number is blank on the line item of the feeder system document. Ideally you would want to link this custom logic to a custom maintenance table in ECC so that you can easily change the material number that is sent to GTS without having to change the code.
3. Override the error message by changing the message type to a warning or informational message (not recommended because this would require a small code modification because I don't think the message type is configurable for this error). Even if you did make this code change you would likely run into more issues in GTS because license determination and other GTS services need a material number to function properly.
Hope this helps.
Sascha

Tax Code for Import Purchase Order

Hi Experts,
I have searched for this content but didn't match my requirements.
My client has asked to create new tax code which they will be using in their Import Purchase order.
Attached along the client's requirement.I haven't created tax code of this nature.
Please advise which condition types should be used to create this tax code.
Kind regards,
Pradeesh.P

Your client requirement is correct in the sense , they need to new excise rates for one combination.
import procurement works differently.
We use dummy tax code here and actual excises will be shown with pricining schema .
For all import procurement , one need to use a separate pricing Schema and all tax values are entired manually while creating PO or cdn records are maintained.
The excises are captured as CVD - Countervailing duties and separate registers are maintained in configuration.
please note - Most of the cases there will be 3 pricing schema - domestic, import ,STO
the import process is also slightly different.
Me21n,MIRO(called commercial invoice @ for customs clearing),J1iex(cenvat capture with addtl-ref-commercial invoice),MIGO,CEnvat post ( cenvat post with addtl-ref-commercial invoice)
a particulat item will contain these cdn details
Basic Price
Landing changes
Insurance
Accessible value
Basic Customs Duty
CVD
ECESS
SHE CESS
Coustom Ecess
Coustom SHECess
Additional Duty
regards
manu

Service purchase order bapi_po_create1 error: maintain services or limits

I am trying to create service Purchase Order.
I am getting error: 'Purchase order still contains faulty items, Please maintain services or limits'.
Struggling to solve this. Can anybody shed some light on this to solve.
I would appreciate your any help.
thanks.
The following is the code I am working.
REPORT ZAUTO_PO_CREATE1                        .
constants: c_x value 'X'.
DATA: i_poitem TYPE STANDARD TABLE OF bapimepoitem,
i_poitemx TYPE STANDARD TABLE OF bapimepoitemx,
i_poitem_sch TYPE STANDARD TABLE OF bapimeposchedule,
i_poitem_schx TYPE STANDARD TABLE OF bapimeposchedulx,
i_acct_*** TYPE STANDARD TABLE OF bapimepoaccount,
i_polimits type standard table of BAPIESUHC,
i_acct_assx TYPE STANDARD TABLE OF bapimepoaccountx,
i_services TYPE STANDARD TABLE OF bapiesllc ,
i_srvacc TYPE STANDARD TABLE OF bapiesklc,
i_return TYPE STANDARD TABLE OF bapiret2,
wa_header TYPE bapimepoheader,
wa_headerx TYPE bapimepoheaderx,
wa_poitem TYPE bapimepoitem,
wa_poitemx TYPE bapimepoitemx,
wa_poitem_sch TYPE bapimeposchedule,
wa_poitem_schx TYPE bapimeposchedulx,
wa_acct_*** TYPE bapimepoaccount,
wa_acct_assx TYPE bapimepoaccountx,
wa_services TYPE bapiesllc,
wa_srvacc TYPE bapiesklc,
wa_return TYPE bapiret2,
wa_BAPIESUHC type BAPIESUHC,
ws_po TYPE bapimepoheader-po_number.
data: wa_it_xlikp like line of it_xlikp.
loop at it_xlikp into wa_it_xlikp.
endloop.
data: wa_it_xlips like line of it_xlips.
loop at it_xlips into wa_it_xlips.
endloop.
data: wa_it_xvbpa like line of it_xvbpa.
loop at it_xvbpa into wa_it_xvbpa.
if wa_it_xvbpa-parvw = 'SP'.
wa_header-vendor = wa_it_xvbpa-lifnr.
endif.
endloop.
*data: it_komp type table of komp,
     wa_it_komp like line of it_komp.
     loop at it_komp into wa_it_komp.
     endloop.
service PO is only for YLF delivery type.
if wa_it_xlikp-lfart ne 'YLF'.
exit.
endif.
shipping conditions.
*case wa_it_xlikp-vsbed.
*when '3P' or 'CP'.
*exit.
*endcase.
wa_header-doc_type = 'YB'.
wa_header-creat_date = sy-datum.
wa_header-created_by = sy-uname.
wa_header-vendor = '0005000000'.
wa_header-comp_code = 'OB01'.
wa_header-purch_org = 'OB01'.
wa_header-pur_group = 'OB9'.
wa_header-CURRENCY = 'USD'.
wa_header-vper_start = '20061118'.
wa_header-vper_end = '20061126'.
wa_header-ref_1 = 1.
wa_header-incoterms1 = 'AOS'.
wa_header-incoterms2 = ''.
wa_header-our_ref = 'N'.
wa_headerx-comp_code = c_x.
wa_headerx-doc_type = c_x.
wa_headerx-creat_date = c_x.
wa_headerx-created_by = c_x.
wa_headerx-vendor = c_x.
wa_headerx-purch_org = c_x.
wa_headerx-pur_group = c_x.
wa_headerx-vper_start = c_x.
wa_headerx-vper_end = c_x.
wa_headerx-ref_1 = c_x.
wa_headerx-incoterms1 = c_x.
wa_headerx-incoterms2 = c_x.
wa_headerx-our_ref = c_x.
wa_poitem-po_item = '00010'.
wa_poitem-short_text = 'Automatic generation - Freight'.
wa_poitem-plant = '0089'.
wa_poitem-quantity = '1'.
*wa_poitem-MATERIAL = '10'.
wa_poitem-NET_PRICE = '23.00'.
wa_poitem-po_unit = 'ACT'.
wa_poitem-item_cat = 'D'.
wa_poitem-acctasscat = 'K'.
*wa_poitem-matl_group = 'S1'.
*wa_poitem-pckg_no = '10'.
APPEND wa_poitem TO i_poitem .
wa_poitemx-po_item = '00010'.
*wa_poitemx-po_itemx = c_x.
wa_poitemx-short_text = c_x.
wa_poitemx-plant = c_x.
wa_poitemx-quantity = c_x.
wa_poitemx-net_price = c_x.
wa_poitemx-po_unit = c_x.
wa_poitemx-tax_code = c_x.
wa_poitemx-item_cat = c_x.
wa_poitemx-acctasscat = c_x.
wa_poitemx-matl_group = c_x.
wa_poitemx-pckg_no = c_x.
APPEND wa_poitemx TO i_poitemx.
wa_poitem_sch-po_item = wa_poitem-po_item .
**wa_poitem_sch-delivery_date = ''.
APPEND wa_poitem_sch TO i_poitem_sch.
wa_poitem_schx-po_item = wa_poitem-po_item.
wa_poitem_schx-po_itemx = c_x.
wa_poitem_schx-delivery_date = c_x.
APPEND wa_poitem_schx TO i_poitem_schx.
wa_acct_***-po_item = wa_poitem-po_item.
wa_acct_***-serial_no = 01.
wa_acct_***-gl_account = '5210'.
wa_acct_***-co_area = 'OB01'.
wa_acct_***-costcenter = '36089'.
wa_acct_***-funds_ctr = 'DUMMY'.
APPEND wa_acct_*** TO i_acct_***.
wa_acct_assx-po_item = wa_poitem-po_item.
wa_acct_assx-serial_no = 01.
wa_acct_assx-po_itemx = c_x.
wa_acct_assx-serial_nox = c_x.
wa_acct_assx-gl_account = c_x.
wa_acct_assx-co_area = c_x.
wa_acct_assx-costcenter = c_x.
wa_acct_***-funds_ctr = c_x.
APPEND wa_acct_assx TO i_acct_assx.
*services/ limits
*wa_BAPIESUHC-limit = '3000.00'.
wa_BAPIESUHC-EXP_VALUE = '300.00'.
wa_BAPIESUHC-no_limit = 'X'.
*wa_BAPIESUHC-NO_FRLIMIT = 'X'.
append wa_bapiesuhc to i_polimits.
wa_services-pckg_no = '20'.
wa_services-line_no = '2'.
wa_services-service = '0005000000'.
wa_services-subpckg_no = '10'.
wa_services-quantity = '100'.
wa_services-gr_price = '100'.
wa_services-userf1_txt = 'TEXT'.
wa_services-from_line = '1'.
wa_services-to_line = '2'.
APPEND wa_services TO i_services.
wa_srvacc-pckg_no = '20'.
wa_srvacc-line_no = '1'.
wa_srvacc-serno_line = '02'.
wa_srvacc-serial_no = '02'.
wa_srvacc-percentage = '100'.
APPEND wa_srvacc TO i_srvacc.
CALL FUNCTION 'BAPI_PO_CREATE1'
EXPORTING
poheader = wa_header
poheaderx = wa_headerx
POADDRVENDOR =
TESTRUN =
MEMORY_UNCOMPLETE =
MEMORY_COMPLETE =
POEXPIMPHEADER =
POEXPIMPHEADERX =
VERSIONS =
NO_MESSAGING =
NO_MESSAGE_REQ =
no_authority = c_x
no_price_from_po = c_x
IMPORTING
exppurchaseorder = ws_po
EXPHEADER =
EXPPOEXPIMPHEADER =
TABLES
return = i_return
poitem = i_poitem
poitemx = i_poitemx
POADDRDELIVERY =
poschedule = i_poitem_sch
poschedulex = i_poitem_schx
poaccount = i_acct_***
*POACCOUNTPROFITSEGMENT =
poaccountx = i_acct_assx
POCONDHEADER =
POCONDHEADERX =
POCOND =
POCONDX =
POLIMITS = i_polimits
POCONTRACTLIMITS =
poservices = i_services
posrvaccessvalues = i_srvacc
POSERVICESTEXT =
EXTENSIONIN =
EXTENSIONOUT =
POEXPIMPITEM =
POEXPIMPITEMX =
POTEXTHEADER =
POTEXTITEM =
ALLVERSIONS =
POPARTNER =
***confirms the document creation by database commit.
   CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
    EXPORTING
      WAIT          = 'X'
IMPORTING
RETURN        =
LOOP AT i_return INTO wa_return.
   WRITE wa_return-message.
ENDLOOP.

Fill this tables:
GT_POSRVACCESSVALUES TYPE STANDARD TABLE OF BAPIESKLC,
GT_POCONTRACTLIMITS   TYPE STANDARD TABLE OF BAPIESUCC,
Glauco

Dummy Purchase order

Similar Messages

Maybe you are looking for