Auto Generate Purchase Orders

Am currently testing ahead of a migration to SAP.
Have created a sales order for an item. This item has supplier information entered.
Then tried to use mrp wizard to create a scenario followed by order recommendations but am getting no results in terms of what stock needs to be ordered.
Am I using the correct tool?

Hi Ricky,
In version 8.81 (currently in Ramp-up) you can (almost) automatically create a PO from a SO:
SO -> Logistics Tab -> tick 'Procurement Document'.
When you add the SO, the procurement wizard automatically opens & you can create the PO straight from there.
In the lower versions, the tickbox is called 'Purchase Order' & once you add the SO, you can create the PO after selecting the supplier.
All the best,
Kerstin

Similar Messages

How to setup a release strategy for store generated purchase order

Hi there,
Does anybody know how to setup a release strategy for store/plant generated purchase order? I have a request from our client, but I never cross this before. Please help and let me know the step with every single detail.
Greatly thank for your help.
Kind Regards,
2tea

Please go thru the below Release Procedure and check whether you have maintained all the settings properly.
PO RELEASE STRATEGY
The release code is a two-character ID allowing a person to release (clear, or approve) a requisition or an external purchasing document. The release codes is basically controlled via a system of authorizations (authorization object M_EINK_FRG).
Use SE12, structure CEKKO to check all the fields available for controlling the Purchase Order.
e.g. If the total value for the Purchase Order exceeds 10,000, release strategy 01 is assigned to the Purchase Order. There is only one characteristic created in this example. For controlling the Purchase Order type, create characteristic for CEKKO-BSTYP and the value NB.
CT04 - Create Characteristic e.g. NETVALUE
Click Additional data Table name CEKKO Field name GNETW and press enter
(for currency dependent field, you are prompt to enter the currency which the system then converts the currency of the Purchasing document into this currency)
In the Basic data (X refers to tick),
X Mutliple values
X Interval values
In the Value data, in the Char. value column, type >10000 and press enter
Save your data
CL02 - Class
Class - Create REL_PUR
Class type - 032
Click Create
Description - Release Procedure for Purchase Order
In the Same Classification section, click Check with error
In the Char. (characteristic) tab, type NETVALUE to assign your characteristics to the class
OMGS - Define Release Procedure for Purchase Order Type
Release Group - New entries
Rel.group Rel. Object Class Description
02 REL_PUR Rel. Strategy for PO
Release codes - New entries
Grp Code
02 01
Release indicators
Release indicators Release Description
0 Blocked
1 X Release
Release Strategy
Release group 02
Rel.strategy 01
Release codes 01
Release status 01
Classification Choose your check values
OMGSCK - Check Release Strategies
(make sure there are no error messages)
Once the Purchase Order is not release, buyers will not be able to print the Purchase Order.
Goods Receipts will be shown with Message no. ME 390 - Purchasing document XXXXXXX not yet released.
In 4.6c, Purchase Order with Release Strategy have a tabs at the end of the Header. This allowed the buyers to check the release status of the Purchase Order.
The person with the release authorization have to use ME28 to release the Purchase Order.
Regards,
Ashok

I am trying to generate purchase order and i create a BAPI also which is active. But when i call the BAPI from SYbase Mobile Object RFC then after calling it gives an Error "Conflict when calling a Function Module (Field Length)".

i am trying to generate purchase order and i create a BAPI also which is active.
But when i call the BAPI from SYbase Mobile Object RFC then after calling it gives an Error "Conflict when calling a Function Module (Field Length)".

Hi,
Yeah i tried my Z_BAPI in R3 and then giving some ERROR.
This is my CODE-
FUNCTION ZBAPIPOTV2.
*"*"Local Interface:
*" IMPORTING
*"     VALUE(POHD) TYPE ZPOHD OPTIONAL
*"     VALUE(POITEM) TYPE ZPOITEM OPTIONAL
*" TABLES
*"      RETURN STRUCTURE BAPIRET1 OPTIONAL
data: ls_pohd type bapimepoheader,
         ls_pohdx TYPE bapimepoheaderx,
         lt_poit TYPE TABLE OF bapimepoitem,
         lt_poitx TYPE TABLE OF bapimepoitemx,
         ls_poit TYPE bapimepoitem,
         ls_poitx TYPE bapimepoitemx.
   MOVE-CORRESPONDING pohd to ls_pohd.
   MOVE-CORRESPONDING poitem to ls_poit.
   ls_pohdx-comp_code = 'x'.
   ls_pohdx-doc_type = 'x'.
   ls_pohdx-vendor = 'x'.
   ls_pohdx-purch_org = 'x'.
   ls_pohdx-pur_group = 'x'.
   ls_poit-po_item = '00010'.
   APPEND ls_poit to lt_poit.
   ls_poitx-po_item = '00010'.
   ls_poitx-po_itemx = 'x'.
   ls_poitx-material = 'x'.
   ls_poitx-plant = 'x'.
   ls_poitx-quantity = 'x'.
   APPEND ls_poitx to lt_poitx.
CALL FUNCTION 'BAPI_PO_CREATE1'
   EXPORTING
     POHEADER                     = ls_pohd
    POHEADERX                    = ls_pohdx
*   POADDRVENDOR                 =
*   TESTRUN                      =
*   MEMORY_UNCOMPLETE            =
*   MEMORY_COMPLETE              =
*   POEXPIMPHEADER               =
*   POEXPIMPHEADERX              =
*   VERSIONS                     =
*   NO_MESSAGING                 =
*   NO_MESSAGE_REQ               =
*   NO_AUTHORITY                 =
*   NO_PRICE_FROM_PO             =
*   PARK_COMPLETE                =
*   PARK_UNCOMPLETE              =
* IMPORTING
*   EXPPURCHASEORDER             =
*   EXPHEADER                    =
*   EXPPOEXPIMPHEADER            =
TABLES
    RETURN                       = return
    POITEM                       = lt_poit
    POITEMX                      = lt_poitx
*   POADDRDELIVERY               =
*   POSCHEDULE                   =
*   POSCHEDULEX                  =
*   POACCOUNT                    =
*   POACCOUNTPROFITSEGMENT       =
*   POACCOUNTX                   =
*   POCONDHEADER                 =
*   POCONDHEADERX                =
*   POCOND                       =
*   POCONDX                      =
*   POLIMITS                     =
*   POCONTRACTLIMITS             =
*   POSERVICES                   =
*   POSRVACCESSVALUES            =
*   POSERVICESTEXT               =
*   EXTENSIONIN                  =
*   EXTENSIONOUT                 =
*   POEXPIMPITEM                 =
*   POEXPIMPITEMX                =
*   POTEXTHEADER                 =
*   POTEXTITEM                   =
*   ALLVERSIONS                  =
*   POPARTNER                    =
*   POCOMPONENTS                 =
*   POCOMPONENTSX                =
*   POSHIPPING                   =
*   POSHIPPINGX                  =
*   POSHIPPINGEXP                =
*   SERIALNUMBER                 =
*   SERIALNUMBERX                =
*   INVPLANHEADER                =
*   INVPLANHEADERX               =
*   INVPLANITEM                  =
*   INVPLANITEMX                 =
ENDFUNCTION.
i am trying to generate purchase order and i create a BAPI also which is active. But when i call the BAPI from SYbase Mobile Object RFC then after calling it gives an Error "Conflict when calling a Function Module (Field Length)".

Generate Purchase Order with Adobe Forms.

Hello SAPients!
Can someone give me a general idea of the steps that I have to follow to generate the Purchase Order as an Adobe Form?
Thanks!

PLS CHECK THIS IF USEFUL
http://help.sap.com/saphelp_nw2004s/helpdata/en/44/bca11fc60b7006e10000000a155369/frameset.htm

Auto matic Purchase order

Dear All
Can we define a default Purchase order document type for automatic Purchase orders.
In My company I have different documents for PO Creation.
1) Domestic,(ZDNB)
2) Imports,(ZINB)
3) Subcontracting,(ZSNB)
4) Misclaneous,(ZMNB)
I like to raise all this Auto Purchase orders in ZMNB
is it possible
Regards
Chaitanya

Hi,
If you want to default the PO doc type for the Automatic Purchase order in ME59N, it is possible for only 1 PO doc type.
As you have 4 types of PO doc types for different purchasing process.
But SAP has provided only 1 option for entering the default PO doc type for ME59N transaction.
Check the IMG settings
SPROMMPurchasing ---Define Default Values for Document Type
hope you got it.
rgds
gsc

Generating purchase order idoc, when a sales order is created

Hi folks,
       we need to send purchase order idoc from SAP to some external system. Once sales order is created, it should automatically generate the purchase order idoc and send to the external system....Any document showing step by step configuration to do so? I have basic knowldege of ALE and IDOC...please suggest me the configuration steps in detail...
           Thanks in advance,
             Shyam.

Hi,
1. Configure the IDoc with message type ORDERS and basic IDoc type as ORDERS05 (You have to follow common step-by-step approach)
2. Configure Message Control to automatically generate IDoc whenever a Sales Order is created. (I mean output type)
So whenever a Sales Order is created, output type will generate an IDoc.
Hope this information is useful.
Regards,
AK

Generating Purchase Order forms in background

Hi!
I initially posted this thread in the MM Forum, but I was encouraged by a user to post it here. Please make me know if this isn't the right place.
I have a little problem regarding the creation of the forms for Purchase Orders. I want the forms to be generated in the background in order to do the delivery when the forms are being generated, which right now I can't. Can anybody tell me if this option is available an where?
Thank you very much in advance for your help.

Hi,
When you say generation po forms in background, do you want forms to be downloaded in background ?
Best regards,
Prashant

How I can automatically generate purchase orders in SRM?

Hi Gurus,
When I create a Shopping Cart (SC), in "Source of Supply" tab I can select a contract as source of supply.
How I can automatically generate a purchase order (PO) with contract data (vendor, price, etc.)? So that the operational purchaser does not have to enter the system to generate the PO.
In ERP (ECC 6.0) exists ME59N transaction, is there something similar in SRM?
The system is:
Component software: SRM_SERVER
Release: 700
Level: 0008
Support package: SAPKIBKV08
Thanks in advance and best regards,
Alonso Valenzuela

Hi,
Like ME59, there is no option available to create a PO automatically in SRM. If you want you can achieve this in 3 ways.
1. Creating SC Via CATALOGS ( In this case after approval PO will be created directly and most of the cases PO will be transferred to ECC i.e in SRM that will be in ordered status.
2. You can select the sourcing relevant indication as 'Never Carried out' (Here if you created a SC without source of supply then all such SC's will be converted into Save status PO's.
3. Do the modification in DOC_CHECK_BADI to force all SC converting to PO.
However in Case 2 & 3, still buyer's team manual intervention will be more, then need to update the PO with source of supply.
Regards,
Govardhan.

Changing Item Text Auto in Purchase Order

Hi All,
   In existing purchase orders, i like to add two text lines to the last line item in the tab 'Texts'.    First i have to read the text lines for the last item. Then i have to add lines to the item. Would anyone know what bapi to make the text changes on the bapi ?
thanks
Joyce

Hi Joyce,
You can use as below:
DATA: lt_lines        LIKE tline OCCURS 0 WITH HEADER LINE,
      lt_header       LIKE thead, " long text
      lc_tdformat     TYPE tline-tdformat VALUE '*',"Tag column
      lv_message(132) TYPE c.
*-SAVE TEXT in - 'Bill of lading Instructions' of Delivery
    lt_header-tdobject = 'VBBK'.
    lt_header-tdname   = gv_delivery.
    lt_header-tdid     = 'Z050'.
    lt_header-tdform   = 'SYSTEM'.
    lt_header-tdspras = sy-langu.
*-CALL FUNCTION 'SAVE_TEXT' - To save text in the Delivery
CALL FUNCTION 'SAVE_TEXT'
     EXPORTING
       client                = sy-mandt
       header                = lt_header
       savemode_direct       = gc_x
     TABLES
       lines                 = lt_lines
     EXCEPTIONS
       id                    = 1
       language              = 2
       name                  = 3
       object                = 4
       OTHERS                = 5.
Thanks
Satyasuresh

IDoc outbound function module to generate Purchase order PORDCH IDoc

Hi all,
Can anyone help me with the outbound function module to generate PORDCH IDoc

instead of that you can use the Below For PO's.
Message Type : ORDCHG
Process Code : ME11
Function : IDOC_OUTPUT_ORDCHG

Purchase order vendor unknown

Hi Experts,
I am creating purchase order with vendor unknown.( ME25) from a purchase requisition. I have created a material with automatic P.O. an source list tick on as well as vendorwith auto p.o. tick on. Alos created inforecord for the material and vendor.
But while carrying out " Generate Purchase order " ;system is not creating purchase order. Can anybody tell me where I am wrong or what are the settings which are missing.
Secondly, is it required that the purchase requisition is mandatory for creating P.O. with vendor unknown.
Regards,
A.Aaditya

Hi,
Few points:
1. You shd always have vendor defined for your PO.
This is req. Because PO is an external document. So, one shd always be aware for which vendor your PO is being made.
2. Assign your vendor in PIR or source list.
Regards
Priyanka.P

Creation of Purchase order by batch run after saving the Service order !

Hello guys,
I am quite new comer, can anybody tell me how to setup a batch job to create the purchase orders once the service order has been created.
Thx
Kami

Hi,
You can maintain source list Tcode ME-01 and make it MRP relevant by selecting Sorce list MRP relevant. In sorce list you can maintain vendor and material data valid for particular period and make it MRP relevant.
With this you can automatically generate purchase order from Purchase requisitions after MRP Run.
Regards,
Tushar Patankar

Creation of Purchase Order automatically via PR after mrp run.

Hi Experts,
I want to know that , after MRP run i got the no of PR'S. As i know , through MD04 i can create purchase order from particular pr but is their any option from which purchase order get generated automatically from pr's which are generated afrer MRP run.
Thanks n Regards
Anupam

Hi,
You can maintain source list Tcode ME-01 and make it MRP relevant by selecting Sorce list MRP relevant. In sorce list you can maintain vendor and material data valid for particular period and make it MRP relevant.
With this you can automatically generate purchase order from Purchase requisitions after MRP Run.
Regards,
Tushar Patankar

Error of PO - "Purchase Order Does not exists"

Dear Experts,
Here i am facing one error of Purchase Order Creation and its further processing.
I have created purchase order and saved it, system issued message that, Purchase Order XYZ is created. (I have taken trial for 2-3 Purchase orders).
When, i am posting Goods Receipt for the PO, system is issuing the error message, Purchase Order does not exists.
Also in ME2M (PO list display) and Me23N (Display PO),
system is issuing the same message - Purchase Order Does not exists, but in PO Creation it is generating Purchase order normally.
Here is no matter of release strategy, because, PO release is not configured.
Dear Experts, Please guide me on the issue !
Thanks in advance !!!!

there can be hundred of different reason for a failure. Most common reason is a problem with the number ranges, e.g. system tries to create a record with a number that is already there.
This can happen if the number range was reset (or transported from a developement system).
But transaction SM13 gives you all the details.
There you see a line for each posting failure. Double click this line again to get more details.
There you will certainly find a line in red that indicates in which function the failure ocured.
Double click this red line to get more info. Use the buttons above to see the content of the posting. For some failures you can create a dump that gives you much more details.
Best you sit together with an ABAPer who can certainly tell you more how to read a dump and how to find the reason.

User Exit / BAdI to update the pricing conditions of the Purchase Order

Hello SAPients,
This is my requirement:
"Copy the Pricing Conditions from the Shipment Cost Document (VI01 / VI02) to the automatically generated Purchase Order".
I'm using the enhancement V54U0002 (Function Module EXIT_SAPLV54U_002) to EXPORT the values of the Pricing Conditions to memory and I have used the enhancement MM06E005 ( FM EXIT_SAPMM06E_006, 007, 012, 013, 014, 016, and 017) to IMPORT the values from memory and store them in TKOMV. But, when the PO is generated the values don't stay, they are always changed with the standard PBXX pricing conditions.
My question is: Does anyone know the User Exit / BAdI that I can use to change the Pricing Conditions of the Purchase Order?
<<removed_by_moderator>>
Thanks!
Edited by: Vijay Babu Dudla on Jan 14, 2009 11:08 PM

>
kartik tarla wrote:
> check this badi
> ME_PROCESS_PO_CUST
>
> and the following user exit
> Goto-> include RV61AFZA then search for
> USEREXIT_PRICING_RULE see if its helpful to u.
Hello Kartik / SAPients,
I tried with ME_PROCESS_PO_CUST but didn't work. The system doesn't execute that code. Any other idea would be greatly appreciated.
Thanks.

Auto Generate Purchase Orders

Similar Messages

Maybe you are looking for