Implement Limit PO functionality in extended classic

Hello Geeks,
I have an issue while trying to implement the Limit PO functionality in SRM 5.0 this extended classic scenarion, initially this functionality was supperessed using BADI, but now it was invoked.
I could now successfully create Limit SHC and PO is generated in SRM, but while transferring of the PO to backend it gives me an error message.
I have not done any addtional settings either in SAP R/3 or SRM to implement this new Limit PO funtionality. Just only I have activated thru the BADI which has been suppressed.
But I get an error message when the PO is created and I can see the RZ20 error message as
"Combination of GR/IR control not allowed for external services"
However I have not mainatined the GR/IR in the vendor master record either in R/3 or SRM, but still I get the same message.
Please suggest me how to avoid this error message and post successfully the PO in R/3
Thanks
Regards
Srujan

Hello Srujan,
There can be several causes for this issue, but only analysing and debugging we could provide a solution.
You have to create a test data for BAPI_PO_CREATE1 and analyse it in your ERP system.
One recurring issue is the following: the structures POITEM and POITEMX may not be aligned regarding fields GR_NON_VAL and GR_BASEDIV.
If POITEM contains values in any field then an 'X' should also be present in that corresponding field at POITEMX. If they are not aligned, this error can be raised. To fix it, use the BADI BP_PO_INBOUND -> Method MAP_BEFORE_BAPI in R/3 side and set the "POITEMX" values to 'X' only when those flags
are set to 'X'
Regards,
Thiago Salvador

Similar Messages

Limit shopping carts in extended classic scenario

How can we implement limit shopping carts in extended classic scenario. Has anyone done it? Thanks in advance

Hi
Which SRM version are you using ? It's possible to implement limit items concept in ECS Scenario.
What exactly you are looking for ?
Please have a look to the following links as well.
http://help.sap.com/saphelp_srm50/helpdata/en/40/654d216f12754e9decdaf4d360bc1c/frameset.htm
http://help.sap.com/saphelp_srm50/helpdata/en/d1/77623c44696069e10000000a11405a/frameset.htm
Few SAP OSS Notes to refer in this case.
Note 712702 ECS shopping cart with several limits
Note 724261 Limit: Error during creation of local purchase order
Note 694442 Limit SC: Customer fields not transferred to backend PO
Note 690000 Limit SC: Customer fields not transferred in Backend PO
Note 699255 Internal note and vendor text for LimitPO and LimitPReq
Note 501977 Error with limit SC: "Unit measure has no ISO code"
Note 520514 Limit, BBP_PD148: No account assignment details were adopted
Note 514727 Limit: Contracts are not displayed in the status
Note 516444 Account assignment check in the shopping cart with limit
Note 515500 Limit:'Confirmation and invoice' indicator not transferred
Note 515695 Invoice entry for limit shopping carts not possible
Regards
- Atul

Has anybody implemented SUS in SRM 5 - Extended classic - pls help

Hi There,
I would like to hear from anybody who has implemented SUS in SRM 5 - Extended Classic.
A client of mine is considering implementing SUS - SRM 5. I cannot find any SAP SUS related docuemntation for the Extended Classic scenario.
Do you have any helpful imformation i.e setup,config and tips that you can share with me.
Many thanks for your help in advance.
Thanks,
Sheena

Hi Sheena,
Please have a look at the link:
https://www.sdn.sap.com/irj/scn/wiki?path=/display/srm/business+scenarios
Here you will find usefull information, like:
https://service.sap.com/~sapidb/011000358700002897382004E/Plan-DrivenwithSInew.pdf
Regards,
Peter

Invoicing Plan functionality in Extended Classic scenario

Hi,
For PO's are created in SRM-Extended Classic scenario, kindly let me know on how to maitain Invoicing plans.
Thanks,
KB

Hi. You could use ERS.
Let's say you wanted an invoice plan to pay every month for 12 months, you could create a cart on an ERS vendor and order quantity 12, unit months.
Then every month the user could do a goods receipt for 1 month.
That would trigger an ERS invoice, just like an invoice plan would.
The only problem with this is that you are relying on the user to do the goods receipt.
Regards,
Dave.

Partner functions OA and IP missing for Vendor in Extended classic PO

As part of current Classic scenario, we have maintained OA (Ordering Address) and PI (Invoicing Party) for a vendor in R/3. We have also maintained different ordering addresses for multiple plants in the Vendor master: Partner functions screen --> Alternative data.
I would like to acheive the same functionality in Extended Classic scenario. We have replicated the vendors from R/3 to SRM. After activating Extended Classic scenario, we see only VN as the partner function in R/3 PO.
Q1. How can we enable OA and PI partner functions in R/3 PO (Extended Classic) ?
Q2. How can we enable different ordering addresses for multiple plants in R/3 PO (Extended Classic) ?

Hi
Which SRM Server are you using ?
You need to maintain Partner Functions in the SRM Server - SPRO Transaction - Configuration Settings.
Here is the Path from SPRO Transaction ->
Supplier Relationship Management -> SRM Server -> Cros Application Basic-Settings -> Define Partner Functions
Maintain Similar entries as mentioned below.
Function Function Type Usage Description Abbreviation
00000016 0013 B2B Requester RQ
00000017 0007 B2B Contact Person CP
00000018 0011 B2B Bidder BI
00000019 0012 B2B Vendor VD
00000020 0002 B2B Goods Recipient GR
00000025 0014 B2B Portal Provider PP
00000026 0008 B2B Responsible Employee RE
00000027 0017 B2B Ship-To Address DP
00000028 0003 B2B Invoice Recipient IR
00000029 0015 B2B Invoicing Party IP
00000030 0018 B2B Ship-From Address SP
00000034 0002 B2B Plant PLNT
00000038 0001 B2B Sold-to Party ORDR
00000039 0026 B2B Preferred Vendor PRVD
00000051 0019 B2B Purch. Org. Auth. For Release AREL
00000074 0025 B2B Service Agent SERV
00000075 0031 B2B Location LOCA
00000097 0034 B2B Invoicing Party Employee IPEm
Hope this will definitely help.
More details ->
For 1), see these links below ->
Partner function missing in backend PO
Re: Error in transmission while PO cration
"Multiple" partner data at PO header
Partner functions in plan driven MM-SUS
Re: Partner function not found
Number range for business partner
Re: Problem with BP. Assignment: Business partner person to user not unique
Error in creation of Employee for Business Partner
Re: enter exactly one partner of type vendor
Re: Business partner as Vendor and Invoicing Party
Partner functions in EBP for extended Classic Scenario
Classic Scenario PO has multiple OA Partner Functions for Vendor
For 2), see the pointers ->
There is an article written by Jason Didday at www.saptips.com entitled "mySAP SRM and SAP R/3 Partner Functions: Supporting OAs, VNs and IPs" that you may find useful.
In SRM, there is no standard relation betwwen plant and vendor master data.
You can use BBP_GET_VMDATA_CF BADI to add backend data in SRM while using BBPGETVD and BBPUPDVD transactions.
Replication of Ordering Address from R/3 to SRM
Re: Adding Partner Function to R/3 PO from SRM in Classic using BADI
Partner function Payee in SRM
Adding Partner Function to R/3 PO from SRM in Classic using BADI
Do let me know.
Regards
- Atul

Extended classic senario with central invoice function

Could we use central invoice function in Extended classic senario, anybody could give us some advice?

Hi. Central invoice lets you enter an invoice against any PO on the system, and normal invoice (desktop user) only allows you to enter an invoice against your own POs.
Both should work in extended classic, I have never heard anything different.
Regards,
Dave.

Use of Purchase info records in SRM SC in Extended Classic scenario

Hi All,
We have implemented SRM 7.13 with Extended classic scenario. If we have Purchase info record in SAP ECC for the material, it gets populated in SRM SC in Source of supply Tab but the price of Purchase info record does not get updated in the SC line item.
Can anyone let me know which configurations is required to fetch the Purchase info record price or we need to have a customization to achieve this.
Thanks,
Ankur

HI Ankur
when you say the price did not get updated did you check the sequence which is used for price determination ?
1. User entry
2. Contracts
3. Info record
If still you think it is an issue please check the report EBP_GET_BACKEND_PRICES and let me know if your problem gets fixed?
Regards
Vinita

Extended Classic Patches. and BBP_LOCATION_GET_ALL. doesn't exist.

Hi SRM GURUS,
I am Implementing SRM 5.5 with Extended Classic scenario, Bidding Engine and Plan driven procurement. I have question, To run this scenario, do we have install any patches?. If yes, what are those please name them. Or tell me where can I find those.
Another question: When I am trying to replicate locations (Plants). I have run the program BBP_LOCATION_GET_ALL.
The systems says that the program doesn't exist. What to do?.
Please explain .... Thanks in Advances.
Regards,
John.

Hi John
BBP_LOCATIONS_GET_SELECTED .check this report too
or location in the report in se38. what are the reports do you get.
is there any syntax error while you search. i smell a rat here.
br
muthu

MM-SUS for the extended classic scenario

Hi,
I have done SUS-MM for the classic scenario.
Did anyone implement SUS-MM for the extended classic scenario ?
Did you face any problem or will it be same as 'classic' scenario ?
Please help
Thanks
Pranav

There shouldn't be any problem especially when the scenarios are concerned. Since the PO's moves from MM-SUS.
Regards, IA

Reverting to classic scenario in SRM7.1, from PPS and extended classic

Hello Experts,
Recently we have moved from SRM7 to SRM 7.01, in which we can have PPS without Extended classic scenario.
As business wants classic scenario, How can we make the system as classic , in which PPS and extended classic is activated.
any badi is available for this? Please help.
Regards,
Raju

Raju,
Basically you have few points to keep in mind. (yes you need to activate the SPRO config for extended classic, apart from this).
1. switch between extended classic and classic is actually defined by the backend logical system of the document. if thats SRM itself then it follows the path of extended classic or if it is ECC then it follows classic.
because its basically creating a follow on document and that explains the scenario.
2. it also depends on what object are you expecting to be created. from a SC many documents can be created.
a. PO in SRM
b. PO in ECC
c. PR in ECC
d. Reservation in ECC
- so, if you can define at any point that where is your document to be created and what is to be created you can control the flow.
Now to do this. if you have few options.
Option1:
1. set the object types(2) for product categories (config, backend document type).
2. implement BBP_EXTLOCALPO_BADI to switch off extended classic
Options 2:
1. in doc change badi, change the backend destination to ECC
2. in Badi BBP_TARGET_OBJTYPE pass the object type you want your follow on document to be.
hope this explains

Payment term key with limit days in Extended Classic Scenario

Hello,
We have an SRM 4.0 implementation (SRM Server 5.0 with Support Package
9) using the Extended Classic Scenario.
When a shopping cart is created, it must be approved, and then a
purchase order is generated (first locally at SRM, and then is
replicated to the backend).
The problem is that the payment term key (field at header level EKKO-
ZTERM) of the backend purchase order is empty, only in cases when we use a payment term key which have several different values for the
field "limit days" (T052-ZTAGG in backend, BBP_PAYTERM-ZTAGG in SRM).
Example:
 ZTERM ZTAGG
 K180 09
 K180 19
 K180 31
If the payment term key selected has no several values for the field "limit
days" (one single entry), the payment term key arrives correctly at the backend purchase order.
Example:
 ZTERM ZTAGG
 E000 00
In SRM table BBP_PAYTERM we have upload the backend payment terms
(using report BBP_UPLOAD_PAYMENT_TERMS). In other threads it is said that you must copy the entries generated by the report with the logical system of the SRM system, but in extended classic scenario it seems to be not necessary.
We have already implemented note 846009, in order to use always the backend payment term, but the error didnt get resolved.
We have our vendor business partners mapped to the local and backend
purchasing organizations, but it is only necessary indicate the Payment term key for the Backend Purchasing Organization.
Regards

hi,
Pls see the foll notes:
Note 576349 - Terms of payment in the ECS
Note 541934 - Modification note: Copying base date from T052
Note 953999 - ECS: Terms of Payment values not in PO header
Note 940453 - Backend payment term data not updated in the extended PO
Note 945018 - Incoterms data not transferred to the back end
BR,
Disha.
Pls reward points for useful answers.

Limit items on extended classic scenario.

Hi everybody.
We are working in SRM 4.0 with extended classic scenario.
We are testing limit items (not service items), but I can not understand the limit item functionality.
In SC, we can assign contracts form limit items. But when we create PO from the SC, there is not any relationship between PO and contract. Moreover when I create a PO (limit item) from null, I can not assign any contract (field is not available).
In the other hand, in SC (limit item), I can select Follow-Up Actions as Confirmation and Invoice or Invoice. If I select Confirmation and Invoice, when I create a PO, ECC return me a message error, because in ECC, good receives are not allowed for PO with limit item category.
So, I have some questions:
1. Can I use limit items in PO with contract reference?
2. If yes, how can I do it? If not, what is the tab contracts functionality in SC with limit items?
3. What is the functionality to allow confirmations in SC with limit items?
4. Is there any documentation about limit item functionality?
Thanks and regards.
Raúl Moncada.

Hello,
As far as I know, this is a technical limitation. A work around would affect other functionalities.
Note 1358679 corrected such issue.
Regards,
Ricardo

SC with Limit Item using Extended Classic Scenario?

Hello,
Can we implement SC with Limit Item using Extended Classic Scenario.
I mention that we replicate the Product Categories from R/3 backend.
We have tried to create a SC with Limit item, but the data on Quantity, Price and Tax is not picked up at PO level.
Regards,
Shaiek

Hi
Please try out this.
For the time-being,
Try de-activating all the custom BADI Implementations and check, what is happening, in the standard SRM system. How does it behave incase of limit item ?
Incase it works fine, without any Custom Implementation active in the system, I suspect there is something wrong in your current deactivated BADI Implementation.
Since i don't have access to your system , Please paste the code here.
Hope this will help.
Please reward suitable points.
Regards
- Atul

Why extended Classic is implemented

Hi Everybody,
I was working in SAP SRM for past 3 years and only Support Experience. Yesterday attended an interview and he asked me why your client has implemented Extended Classic why not Classic Scenario?
I know it depends to client-to-client.
Can any one let me know the list of points need to be discussed to support this question. My answer was not impressive.
Sree

Hi Sree,
You are right here it depends on the client whether to configure the system for extended classic and classic scenario.
The extended classic scenario suits customer who wants to
their purchasing department to save time and money by using the streamlined purchasing functionality of SAP SRM
use the full sourcing capabilities offered by SAP SRM, yet who also want to be able to confirm and invoice direct materials
the flexibility of being able to pre-enter confirmations and invoices
Where the classic scenario suits the customer who wants:
wide user group, for example employees not necessarily working in the purchasing department, to be able to enter their requirements quickly and easily. SAP SRM’s functionality and ease of navigation allow this, as it requires only minimal training
their purchasing department to operate solely with the functionality offered by the backend system(s)
For whom a transfer of purchasing activities to SAP SRM is not viable in SAP SRM
You can use both the classic and extended classic capabilities by configuring the product categories
Please let me know if the above answer is helpful.
Best Regards,
Ankit Jain

'BAPI_POEC_CREATE' function doesn't work with extended classic scenario

Hi everybody.
Antecedents:
We are working in an extended classic scenario.
When we create a Purchase Order via ITS in SRM, the system works ok, the PO is replicated in the ERP system.
But when we execute BAPI_POEC_CREATE function module in order to create a PO in SRM, no message are available in the application monitor, but the PO is not replicated in the ERP system.
Both exampled were created with exactly same data (partners, items, categories, accounts, )
Moreover when we modify the second PO created via ITS, the systems doesnt show any error message, we can order our PO again without error, but the PO isnt replicate in the ERP system.
1. We executed BAPI_POEC_GETDETAIL function module, and there is only a difference between POs, E_PO_STATUS table.
PO created by transaction has 8 entries:
       I1009 X
       I1015 X
       I1021
       I1038
       I1039 X
       I1043
       I1080 X
       I1180
And PO created by BAPI has 5 entries:
       I1015 X
       I1021
       I1038
       I1043
       I1180
2. We run BBP_PD transaction, and there is only a difference.
PO created by transaction mode shows:
- Message: W BBP_PD 830 Default values have been taken from Vendor PRUEBA10/purchasing organization Área Global Compras (org. compras)
And PO created by BAPI
- Message: No Messages
Could anyone help me with the problem?
Thanks in advance.
Raúl.

Hi Raúl,
this is exact, BAPI_POEC_CREATE is designed to create local PO.
If you want to replicate it to R/3, then you have to change it to an ECS PO.
In BADI BBP_DOC_CHANGE_BADI, called at the real beginning of BBP_PD_PO_CREATE, you will have to change some data to enable the ECS scenario:
- change header subtype to EP
- change header log system to SRM (keep FI LS as is)
- determine a backend purch group & org
- complete BE fields (be_object_id, be_object_type, don't change be_log_system because it will be determined during the transfer, be_pur_org and be_pur_group will also be determined during the transfer)
- ... and maybe other R/3 relevant fields
Compare both PO one by one, and adapt the gaps.
Rgds
Christophe
PS: please reward points for helpfull answers

Implement Limit PO functionality in extended classic

Similar Messages

Maybe you are looking for