PR adopt From SO

Dear Expert,
Can anyone knows how to make Purchase Requisition automatically create from Sales Order ?
where i can customize in IMG ?
Best regards,
Korintus

Hi,
You are referring to Third Party Sale process. There are many replies in forum, you may try to check those also.
1. Business gets the order from customer and it passes to the 3rd party vendor who delivers the goods to customer and bills the Business.
2. 3rd party order is controlled via material type eg: trading goods (HAWA)
3. Item category group is BANS and item category is TAS.
4. When you create sales order with third party material, system automatically creates the PR.
5. During creation of the PR, system automatically determines the vendor. PO is created.
6. Configuration you need: customer XD01, Material MM01, Vendor: XK01.
7. Schedule line is CS, In order type there is NB, which triggers automatic PR when you save sales order.
8. After you save sales order, go to va02, select material, and check in schedule line, you can see the PR no.
regards
Vandy
Edited by: vandy.kuk on Sep 27, 2011 6:22 AM

Similar Messages

How to make the price in PO to adopt from info-record and not changeable?

Hi Xperts,
Can somebody explain to me how to set the PO price to be adopted from the info-record and is NOT CHANGEABLE at the creation and change of PO screen. I know that i can configure the field selection for the PO type to be "price as display" only. Any other solution?
Thanks.

Hi!
tick the check box info-update at the item detail under master data tab in a PO.
its significance is as follows:-
Info record update
    Determines whether the prices and conditions of this purchase order item
    are suggested in future PO items.
Use
    Selecting InfoUpdate causes one of the following situations to occur:
        -   If just one info record (with or without plant) exists, it is
            updated.
        -   If no info record exists and "plant condition requirement" was
            specified in Customizing, an info record with plant is created.
            Otherwise, an info record without plant is created.
        -   If two info records exist (that is, one info record with plant
            and one without plant) the info record with plant is updated.
Dependencies
     You can specify that prices and conditions in purchasing info records
     are only allowed at plant level in the Purchasing IMG, under Conditions
     -> Define Condition Control at Plant Level.
Hope this helps you,
Regards,
Archit.

SES not pulling correct price when adopting from Contract

When doing a service entry sheet against a Limit Purchase Order and
adopting a service master from a contract the price that is being
pulled into the SES appears to be from the last purchase document
instead of the specific contract line item that is being adopted. When
we adopt a service master line item from a contract for say $4.00 we
are expecting $4.00 to be populated on the SES. Instead we are seeing
a price of $3.00 which happens to be the price of the last purchase
order where this service master was referenced. How can we get the
system to pull in the service master from the contract with the
contract pricing?
Steps for Reconstruction
1. Select Contract from which to Adopt Service Master - the user is
doing a service selection and choosing to adopt the pricing from
Contract 5600000119, line item 2.
2. Select Services to Adopt to SES - the user identifies which
Service Masters they wish to adopt on the SES. Note the cost is $4.00
for each of the first two service masters and $6.00 for the last one.
3. Adopted Service Masters come in with incorrect pricing - once
these Service Masters are adopted from the Contract to the SES they
come in with incorrect pricing. $1.75, $3.00 and $1.75 instead of
$4.00, $4.00 and $6.00.

Hi,
Can you confirm the following :
1. What is the price maintained when creating teh service contract.
2. was the service selection when creating services in limit PO done referencing the contract?

How to disable text can be adopted from inforecord (PO text)

Hi,
I have a issue in PO output, when I try to create a PO through ME21N transaction, the inforecord PO text is not printing in PO output.
It is printing only when I click on the option text can be adopted from inforecord (PO text).
This option is there in item details text tab.
Please let me know how to disable this option, because when I create PO automatically, it is not printing inforecord PO text.
Here we almost all PO's create through automatically, so we should not have any restriction to print this.
When we create PO, automatically the text should print.
Please advise.
Thanks,
Sandhya

In customizing for purchasing , under SPRO -? materials management-?Purchasing-? Purchase Order->Texts of rpurchas eorders->define copying rules for item texts , here select 02-info record PO text and click on "text linkages" .
Here for sequence 0 ,"Info record PO text " , the fix indicator should be " " BLANK. In this case, the text should automatically be adopted in the PO , and should come in print

How can i block PO adopt from PR with no release tab

Dear Experts,
I need to block PO creation ( by adoptation of PR) from PR which has no release tab active. Kindly help me how can i do this.
From unreleased PR , PO can not be created and it is standard SAP function. But if PR has no release tab then PO can be created from that PR and no error or warning is there. But i need to block PO creaation from the PR which as no released tab active.
Please help.
Kind regards,
Zusen

Hi Zusen,
Would not be good idea to place those PRs in release strategy? In this way PO(s) will not be created until PR(s) is released. Have a look at release strategy of PR under the path; IMG-Materials Management-Purchasing-Purchase Requisition-Release Procedure
Otherwise you have to develop some coding. You can use BADI: ME_PROCESS_PO in order to control unreleased PR. If EBAN-FRGRL is NULL in PO then you can place an error message as you want.
Kind regards

Price not adopted from Contract using Source list

Hi all!
I have read a few threads related to Source lists and why assignment does not pick up the price from the contract if the contract is the only source, but do still not understand this.
I have a sourcelist with a fix source of supply (Vendor, Contract). During automatic assignment, this contract is picked up correctly, but the price from the material master is retained. Why does the system not adopt the price from the contract?
Appriciate if someone could explain the logic behind this system behaviour.
brgs Ziggy

Hi
Check whether any parameter id (EFB or EVO) is assigned to your id in SU01. If the price is copied from PO, then you will have a parameter id EFB in your user in SU01 which is defined in OMET. EVO is buyer's default. Standard SAP is it defaults from last PO. You define buyer default in customization and stop copying last PO price in your new PO.
Regards
Antony

PO Document Types when Adopting from PRs

We are using 2 docment types for both PO's and Purchase Requisitions (NB and ZX). When using ME59N to automatically generate PO's from requisitions, the PO's get setup with the proper doc type based on the requisitions type (NB requisitions convert to an NB PO, and ZX requisitions conver to a ZX PO).
However, when adopting a requisistion in ME21N, it always uses NB for the PO, no matter what the requisition has. Is there a way to get adopting a requisition to work like ME59N and set doc type on the PO based on the requisition's doc type?
Thanks,
Rick

Std SAP is set defule doc type in the System is NB but if oyu want ZX Doc type in ME21N then you have to create screen variant for this doc type and assign the transaction to do that
Go To SHD0
enter ME21N in Transaction code field
and then enter e.g. ZME21N in Transaciton variant filed then hit create button
it will take you to the PO create screen.
here you enter all the value and and create the PO.
every popup screen hit enter
and which ever value you want to defulat to the transaction
those values you have to check the check box of
W.content and output only
then save. it will ask you the object where you wan to save
if you want to migrate to another system then use the real package other wise use $TMP for each screen (until the popup goes away)
and save it
Then go back to main SHD0 screen and hit goto button and select create variant transaciton and create the tcode for this variant which can be used by user

Table for Subcontracting PO Components (not adopted from BOM)

Hi All,
In which table do the components of a subcontracting PO get stored? This is specifically for a situation involving subcontracting of a material without a standard BOM. I will be feeding the components manually during PO creation. I need to pull the component list in the Smartform. Any idea? In case there's a function module for the same, please help out.
- Rahul

Hi,
Thanks for your reply. But these are all tables related to BOM for the item. My requirement is specifically for an item that does not have a BOM. That's why I am stuck up. Please let me know if there's any table where the component data flows (not from the BOM, from the PO). PO component data is available in the Structure MDPM. How to retrieve the data from Structure MDPM ? Any function module is there for that?
- Rahul.

Adopt net price from contract if po created with referance to contract

Hi expertise,
Can any body so kind to find a way for the below requirement of my client:
When PO is created with reference to contract, the net price of PO should be adopted from the contract & user should not allowed to change the net price of that PO (but allowed to change the quantity).
Your earlier answer should be highly appreciated.
Regards,
Sp sahu

Hi,
You should make use of two very helpful options in SAP.
They are known as the EVO parameter and the EFB parameter. These control what the user can do when generating .
You configure a combination of flags on each parameter and so control things like "can prices be changed", can the user ONLY create by referencing a document (contract or req etc.)
They are configured in the following menu path on SPRO
Materials management > Purchasing > Environment data > define default values for buyers.
This is the EVO parameter it is well worth reading the help text on the config for this. It explains that you have to then add a parameter (EVO) to the userid (in the normal way that they maintain their userid , or via the config).
The EVO parametr is quite useful but the EFB parameter is even better, this conttrols what the user can do.
The menu path for the EFB is
Materials management > Purchasing > Authorisation management > Define function authorisations for buyers.
This is the one that will help with your problem. It works like the EVO parameter and so you add the EVO parameter to the userid and give it the code that relates to one that you have configured (careful the system is case sensitive for these codes, so use upper case or numbers for the codes when you configure them)
In the EFB config switch on or off the flags that you want (in your case switch OFF the enter conditions and it may help to use an appropriate field selection reference key that makes the fields display only.
Then when you allocate this parameter to the userid the settings will apply.
try them out in your play client, they are VERY useful, especially the EFB parameter.
Steve B

Disable adopting price from Info record

Dear Experts,
While creating the PO i don't want the price to be adopted from the Info record ..
I want to disable this function
Thanks in advanced

Hi
Its very easy dear....just remove the access sequense from the basic price condition u are using in ur schema, Basically what i understand is u might be using the SAP standard basic price condition (PB00 / PBXX) these conditions are by default having access sequence assigned. Either just remove these access seq. or create another condition type a copy of the existing one but just remove access seq. and assign this condition type in ur calculation schema in place of present baseic price condition.
In SAP standard conditions there is already one condition type of Gross price for manual price (means without access seq.) u can use that also.
Hope this solves ur problem
Regards
Vineet Baweja

PO texts from vendor master

Hi,
when I create a PO using a vendor, after filling field Purchasing Org., Purch. Group and Company code, system copies a text but I don't know from where.
In PO down the header texts I can read "Text adopted from Vendor Master (Purch.org.-spec.test text )", I cannot find it in vendor master....
Could You help me ?
Regards

Hi,
In MK03 please open your vendor go to purchasing data and click on extras on the menu bar, and select text, here you will find purchase order texts, hope this is what you were looking for.
Also check the PIR.
Regards
Shailesh
Edited by: Shailesh Rajan on Jun 28, 2011 3:07 PM

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
BAPI_PO_Change , 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.

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

regards
prabhu
Message was edited by: Prabhu Peram

Restrict referance of pricing and condition type from latest PO.

Hi Experts,
I am creating Purchase order and at the time of creation of purchase order system is copying prices and condition types from latest PO.
Which is not desirable to our business process, when I dig out I found out that in standard SAP system
The system looks at pricing in the hierarchy order as below:
u2022     Contracts/scheduling agreement
u2022     Condition records
u2022     Info Records
u2022     Last purchase document
So can some one help me with information how to restrict system to follow this referance of pricing.
I want to enter price as well as condition type manualy every time user create a purchasing document.
Also i want to know can it be restricted specificaly for few document type.
Thanks
Best Regards
Ritesh

Hi sir
can we try this
Use the user parameter EVO to indicate that no price adoption from last Purchase Order must take place:
IMG: MM -> Purchasing -> Environment data -> Default values for Buyers
-> Setting for Default values.
Select or setup a default value and on the "price adoption" tab you may choose how copying of conditions from last purchase order must behave. Select "Do not copy".
Then assign this default value to the user, using the EVO parameter.
[http://sap.ittoolbox.com/groups/technical-functional/sap-log-mm/price-to-flow-from-info-record-at-plant-level-813066]
[Re: new info record with same details as archive one.;
check following notes it may helfull
569885 About Info Record Update indicator (EKPO-SPINF)
13127 Update in info record from PO, quotation, contract
430543 FAQ: Purchasing info record
675523
456691
Regards
Kailas ugale

PR Price Adopted to PO for service item

We are using idocs which uses BAPI_PO_CREATE1 to load the legacy PO's into ECC. Even though we supply the PO Price which is different than the PR Price for service item, the price is still adopted from PR which we don't want. I checked ML91 and there is a flag which is "Ignore Requisition Price in PO", but for online process, PR price must be adopted to PO for service item. Any Ideas if something can be done with configuration or any enhancements I have to look at.

Hi,
As you needed, use t.code OMET & define functional authorization, choose u201CAdopt PO Priceu201D and u201CRef. to Purchase Requisition" & save. Now in t.code SU01 assign your user ID with parameter ID EFB.& save. Now create PR & then create PO wrt PR, see the valuation price of PR will be taken to PO automatically.
Regards,
Biju K

Material price to be defaulted in shopping carts from Contracts in ECC

Hi Guys,
We are having a scenario wherein we need to get the price in shopping cart from contracts in ECC.In our case for a material only one contract exists for a given time frame in the ECC.We are working on classic scenario in SRM 5.5 as an add on to ECC.Any help to get this working will be highly appreciated.
Thanks in advance.
Regards,
Pawan.

Hi Pawan,
As long as you dont have the Configuration Step "Sourcing Via Vendor List activated", all contracts that you have created for a material will automatically show up in the source of supply as the proposed SOS. This and Info records are displayed on the SOS tab on the SRM Shopping cart via an RFC call that Standard SRM Does.
Pls try out a scenario:
1.) Create a contract for a material in ECC
2.) Replicate the material in SRM
3.) Create a Shopping cart in SRM with that material
4.) you will automatically see the contract beoing displayed on the SOS.
Following are the pricing priority in SRM.
Price Determination in EBP
Priorities
1.) Manual price (only if field is open for input)
2.) Contract
3.) Catalog
4.) Price from product linkage or from product
So as long as you dont have a manual price for the Shopping cart, the price will be adopted from the contract. i would suggest for materials with contracts, update the s/c price with the BBP_DOC_CHANGE_BADI at the time of submission with an RFC call to ECC to obtain the right proce from the contract.
Hope this info helps !!
Pls assign points, if answer helps you
Sundeep

PR adopt From SO

Similar Messages

Maybe you are looking for