Local Purchasing Organization in extended classic scenario SRM 4.0

Hi all,
I have tried to make settings for updating vendor master records. I used the following path in IMG.
SAP Implementation Guide > SRM Server > Technical Basic Settings > Settings for Vendor Synchronisation > Define Settings for Each Backend System
There i wanted to make the entries for: Order, LogSystem, Flag in NoBEPchOrg and Local Purchasing Org. For the Local Purchasing Org. field i could not select any entries.
My question now is how can I check if there is any local purchasing organization maintained. In the EBP Organizational Structure I have set the flag for the purchasing organization and have entered in the "corresponds to" the number of my purchasing organization from the backend and i have selected the SRM-System in the next field.
Best regards,
Bernd

In the organization structure, under function tab leave the corresponds to field blank

Similar Messages

Question on Purchasing documents in extended classic scenario

Hi friends
How to create local purchasing documents i.e po,confirmations,invoice, in extended classic scenario
Please let me know the path
regards
venkat reddy

Hi Venkat,
The user interface and the process is same for local documents. However the result of document posting (either backend or local) depends on the setting in SPRO --> SRM --> Technical basic Settings --> Define backend system for product category.
Here you can define the target system as the system of document posting. If the terget system specified here is your SRM system, then it will create local documents in SRM.
Regards,
Prashant
Do reward points for helpful answers

Purchase Order Creation, Extended Classic Scenario

Can someone please explain the different databse tables affected during the creation of a Purchase Order.
Also, is there a transaction with which we can create PO in Extended classic scenario?

hi,
below are the tables effected while creation of PO:
CRMD_ORDERADM_H
CRMD_ORDERADM_I
BBP_PDIGP
BBP_PDBEI
BBP_PDISB
BBP_PDISS
BBP_PDSDLN
BBP_PDACC
BBP_PDTAX
BBP_PDATT
BBP_PDORG
BBP_PDWGT
BBP_PDDYN
BBP_PDEXR
PRCD_ITEM
PRCD_COND
PRCD_COND
BBP_PDDEP
CRMD_PARTNER
as far as your second question is concerned normally we will be creating a PO in SRM/EBP in web browser and it will replicate to the backend ERP.
regards
IGA

Purchase order replication – extended classic scenario using XML proxy via PI

Hi Experts
Question:
In case of extended classic deployment is it possible to use XML proxy to
transfer SRM purchase orders to ECC? As we know as of SRM 7.01 its via RFC
whether SRM 7.02 onwards does SAP support XML for ECS too?
Has
anyone read about this in any of the SAP forums?
Background: In our project, client have invested
heavily on XI and XI monitoring and troubleshooting, integrated to SAP SOLMAN.
And would like to opt for XML mode of transfer and reuse existing solution.
This is the main reason we would like to be very clear in our understanding
before we go back to client.
We appreciate your time and support.
Regards
Prashanth

Dear Rahul,
Thanks for you input
Let me give you an example of the behaviour:
in PPOMA_BBP TOG assigned to user has : DQ with $1000 and upper percentage 5%.
User orders a PO with quantity=1000, price $100;
No additional tolerances assigned in the PO itself
User tries to enter confirmation with quantity 1001 (so qty variance converted to currency amount results in $100 over delivery) So the confirmation is under both the 5% and the $1000 limit.
In that case I donu2019t receive an error message from the SRM, but the error message u201CBackend Purchase Order quantity exceeded by 1 EAu201D from ECC still prevents me from posting the Confirmation. And this is the problem I havenu2019t been able to solve so far.
So I want the TOG tolerance to be used. And I am also happy with the absolute limit always having priority over percentage limit...
But I am trying to find a way to get rid of the back end message (with assigning a tolerance to the PO itself as the will get rid of the absolute limit see my previous post.)
Cheers
Ulrike

OPEN purchase order for Extended classic scenario

Hello All,
I want to is there any way to find out Open PO in SAP SRM
like ME2* reports in MM
Can I extract the report via CRMD_ORDERADM* tables?
Thanks
Raman

Hi,
You can try the foll:
1st way is to look into the standard tables in the SRM system
CRMD_ORDERADM_H (Header Data)
and
CRMD_ORDERADM_I (Item Data)
for the Business object type - BUS2201 (Purchase Orders)
2nd way is using BBP_PD Transaction for the Business object type - BUS2201 (Purchase Orders) (The transaction calls the same tables to fetch the details)
3rd way using the standard function modules - BBP_PO_GET_DETAIL / BBP_PD_PO_GETLIST ,In the FM "BBP_PD_PO_GETLIST " ,you have the import parameter "I_IV_OPEN",try to use that for reteriveing the list of open Po's.
BR,
Disha.
Do reward points for useful answers.

Material PO confirmation at supplier side (SUS) not taking place in SRM SUS Extended classic scenario

We have configured extended classic scenario SRM with SUS, and all functions are working fine. However, at the time of PO confirmation of material item at the Supplier side (SUS), the material line item disappears when we click on the Create Confirmation button in SUS. The functionality is working fine for Service Items. The total value of PO is also displayed correctly in the Items overview section.
Please provide some help in solving this issue.

Hello,
This is the correct behaviour of SUS - confirmations can only be created for service items which in turn create service entry sheets (Trx: ML81N in ECC). And accepting the SES in ML81N will generate GR posting.
For material items, you have to create ASN which will in turn create inbound delivery in ECC which you can post and will generate goods movement documents.
So basically, for service items you create confirmation and for materials you create ASN.
Regards,
Prasanna

Error while creating Manual Service PO in Extended Classic Scenario

Hi Experts,
Extended Classic scenario (SRM 7.0 with ECC 6.0) While Creating Manual Service PO in SRM i am getting the below mentioned error messages. Can any one suggest what could be the problem.
Error Msgs:
1. Backend Error:In case of account assignment, please enter acc. assignment data for item
2. Backend Error:Purchase order still contains faulty items
Regards,
Mohan

Hi,
Yes i given all CC and GL information properly in Purchase Order Document for Service.. Still finding the error for Service PO alone.
Pl do the needful
Regards,
Mohan

GOA as SOS (Source Of Supply) in extended classic scenario

Hi,
I understand that when I create a SC in EBP, GOA can't be a SOS in "Extended Classic Scenario (SRM 5.0)". If I want to make GOA as SOS, how do I do it ?
I have searched the forums and found that the below BADIs can be used.
BBP_CTR_BE_CREATE
BBP_CTR_INIT_UP
BBP_CTR_MAIL_BADI
BBP_CTR_MASS_BADI
Now I am looking for someone who has done this scenario and please explain how did you do it ?
With regards,
Pranav

Hi,
I had a former project where I modified SRM standard source so that I can use GOA as source of supply in extended classic scenario. In Standard, as you know, SAP doesn't allow to use GOA as SOS in extended classic. In extended classic, we have to use local SRM contract as SOS. In my case, it was SRM 3.0.
Cheers.

Are you using the Extended Classic Scenario ?

Hello everybody,
Is somebody using the Extended Classic Scenario - SRM 4.0 ?
If yes, could you describe briefly the config steps that you follow ?
I have received and followed some advices here and I have checked all the official documents without success.. =( Until now, for some reason the EBP tries to create the PO in the backend =(
Thanks for your help guys !
Regards from Mexico.
Diego

Hi Diego,
If you activated the Extended scenario, the system cannot try to create directly a PO in the backend, it first has to create it localy.
If you are sure that:
-You activated the Extended scenario in SPRO (and not in the BADI)
-The system tries to create directly the PO in R/3 (as you say in your post)
Then there are only 2 solutions:
1- You have activated the scenario BADI, and tell the system to work in classic scenario
2- You have a bug in your SRM (which I doubt, cause I implemented this scenario on EBP 3.5, EBP 4.0 and SRM Server 5.0, and I never had this kind of problem).
Regards.
Vadim

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

Organization structure in extended classic scenario

Hi All
I am trying to configure extended classic scenario on SAP SRM 7.0. I have made the following settings for the same:
1. In SPRO->SRM Server-> Technical Basic Settings -> Define backend system from product category, I have specified target system as SRM system and not ECD system
2. In SPRO->SRM Server->Cross Application Basic Settings-> Activate Extended Classic Scenario, I have selected all the options including "Back end purchasing group responsible"
I have a few doubts.
1. In organization Structure (PPOMA_BBP) Comapny code is corresponding to company code in back end but do I have to create local purchasing organization and local purchasing group i.e. in Functions-> Corresponds I'll have to leave blank. plz suggest
2. Also is IPC configuration mandatory for extended classic scenario
Plz give your suggestion on above mentioned issue
Regards
Pawan Keshwani
Edited by: pawankeshwani on Mar 18, 2011 8:33 AM

Hi Pawan,
No you should mention Purch Org & Purch Grp also wrt your backend (ECC).
IPC need not be configured separately from SRM 5.0 onwards. To ascertain if IPC is working fine just run the report : RSVMCRT_HEALTH_CHECK. You should see 4 success messages. Else get in touch with Basis to enable Virtual Machine Container (VMC)
Regards,
Nikhil

SRM: Extended Classic scenario: Request your help.

Hi Guru's,
We are implementing the EXTENDED CLASSIC SCENARIO in our project. kindly request your help.
in our project the SRM box is : G3OSBSR102.
R/3 backend Box is : RCHSBR3142.
Now when i create a shopping cart it should create the Purchase order In SRM( G3OSBSR102) and also copy the created purcahse order in teh backend system : RCHSBR3142.
The issue here is which Logical system should be populated in the field at item level when creating the shopping cart :BE_LOG_SYSTEM.
1) In this field: BE_LOG_SYSTEM.
If i populate the SRM local: G3OSBSR102., then it will consider the Business object type as : BUS2201and creates the local Po but while transfering this local created document(PO) to R/3 system is loosing the Logical system at the item level of the PO.
If i populate this field at the item level via DEBUGG mode then system is sucessfull in transferring the document to R/3.
2) In this field: BE_LOG_SYSTEM.
If i populate the SRM local: RCHSBR3142, then it will consider the Business object type as : BUS2012 and creates the purchase order in R/3 system and will not create teh local purchase order.
Kindly request your help for any further settings if i did miss.Appreciate your help in this regards.
Many Thanks,
Prasad NN.

Dear Prasad,
To work on Extended Classic Scenario, you just have to maintain the following configuration in SPRO:
>SAP Supplier Relationship Management
>SRM Server
>Cross-Application Basic Settings
>Activate Extended Classic Scenario
Check the flag "Extended Classic Scenario Active".
You dont have to manipulate "BE_LOG_SYSTEM" field to choose your scenario.
Regards
Thiago Salvador

Extended Classic Scenario-Replication of Local PO to R/3 fails

Hi,
In the Extended Classic Scenario (SRM4.0/ECC5.0),we are creating Purchase Order from the Sourcing Cockpit. Local PO is getting created , but is not getting replicated to Backend R/3.
After debugging through BBP_PD_PO_TRANSFER_EXEC , noticed that all the PO data is available when BBP_PO_INBOUND is called .But the PO number is missing when the BAPI_PO_CREATE1 is called. Because of this , system is searching for internal number assignment and since only external number is assigned for the document type , it is giving error.
Can anyone suggest if we are missing anything.
Regards
garugu

Hello,
this is strange, because in ECS the local PO gets an ID, and this ID is used during the transfer to R/3.
Debug BBP_PD_PO_TRANSFER_EXEC once again to see where this ID is cleared.
To you have activated the BADI BBP_ECS_PO_OUT_BADI to transfer data to R/3 ?
Be carefull, some BADI need to populate all export parameters/tables (E_*) otherwise the inbound data is considered as erased.
Where is the ID disappearing ? in SRM just before calling R/3, or in R/3 ? In that case look at user-exit or BADI is R/3.
Rgds
Christophe

Extended classic scenario local PO Output status

Hello all ,
Need some inputs on extended classic scenario local PO Output.
My requirement is , when ever the put get process successfully in SRM , I need to send a mail to requester saying that u201C for this particular output got processed successfully u201C
I have business requirement, we need to run this report every 30 min, This report has to pull out the all the PO number from the current time to past 30 min, for the output got processed successfully.
To meet this requirement, I am using the output log entry table PPFTTRIGG where we can see the all the PO with the status and time stamp also.
But some how, this table maintaining incorrect time stamp.
Ex: If I create PO, process the PO output, and if I see the time stamp for this PO, its showing as 10 min before the current time.
Did anybody come across this issue? Or can anybody suggest me any alternative approach for this.
I mean is there any function module/ table available, which will give PO Output status also.
Can you please give me any pointers for this?
Seeking your help on this.
Wish you a advance happy new year.
Thank you.

Hi Latha,
Did you have a look at the standard report RSPPFPROCESS. For PO's please pass the below selection screen values along with the appropiate date & time details:
Application = BBP_PD
Action Profile = BBP_PD_PO
Then regarding the time difference, please make sure that the application server time is sync with the actual time of the time-zone. This could also be a reason.
Then what you can do is to clone the RSPPFPROCESS program and add the email notification logic on that.
Please have a look at the BADI BBP_PROCESS_PO, this can be of some help for your requirement.
Hope this solves your problem.
Regards
Kathirvel

Extended classic scenario local PO

Hi All ,
Need some inputs on the extended classic scenario local PO.
There is couple of functionality which we need to do for the PO. I mean when the PO gets created automatically after shopping cart completely approved
We can change the same PO from the process purchase order also.
But if I want to map couple of the fields, when PO is getting created automatically how can do that one. And I donu2019t want map these fields when the PO is from the getting changed process purchase order also.
I am using the BADI, BBP_DOC_CHANGE_BADI (PO_CHANGE Method) to map these fields.
The thing is here , this BADI will call even for the automatic PO creation and also for changing the PO .
Currently when I noticed PO gets created automatically by the user id u201CWF_BATCH u201C , So I am using the same the logic like .
If sy-uname = WF_BATCH
Do the mapping part
Endif,
But I donu2019t think so; this logic will work all the times.
Please can anyone give me some pointer for the same, it will be really helpful for me .
Seeking your help on this
Thank you,

Hi Latha,
This is a bit tricky one. Yes you are vry correct, the logic is not that fool proof, as the PO can be subjected to so many changes back & forth; even approvals can be done after a change is completed etc.
The other alternative is to go ahead the document version. You can use the function module BBP_PD_PO_GETDETAIL and the table E_VERSION will contain all the versions of the PO. This should differentiate the change & initial PO verions.
Hope you can build your logic based on this; this is a better logic on par with the existing one.
Regards
Kathirvel

Local Purchasing Organization in extended classic scenario SRM 4.0

Similar Messages

Maybe you are looking for