Plant Replication Classic Scenario SRM 3.0

Hi,
would anyone remember the report to replicate plants from R/3 into SRM in SRM 3.0
In 4.0 / 5.0 it is
BBP_LOCATIONS_GET_ALL OR
BBP_LOCATIONS_GET_FROM_SYSTEM
But these so not exists in SRM 3.0
This is urgent.
Regards,
Rahul

Other things I have checked are
1) RFc / ALE settings - they are fine as I could replicate the Prodcut Cat from backend
2)Checked the Backend Systems
3)Checked the Product Cat - Backend System.. Here I have selected each Product Category, assigned R/3 as source system and SRM as Target System (IS THIS OKAY)
4) Checked the Pur Grp - Product Cat Assignment. Pur Grp is the Org Str Id of the Pur Grp in SRM. When I select the Prod Cat, it selects the backend system automatically.
Only thing I have not done so far is that I have not replicated the Vendors. When I try to do it, it does not brings any vendors forward either. I thought I will look into this error later. I hope nothing inter-connected

Similar Messages

STO classic scenario SRM 4.0

Hi All,
We create SC that transferred to STO (Stock Transfer Order).
With the Classic Scenario(SRM 4.0) we use BBP_CREAT_PO_BACK.
A STO is created but the number of the STO is not displayed in SC.
Any suggestion ?
Thanks in Advance..
Moti

Hi Christophe
I) In CS - Did you use the scenario were a SC is transferred to a STO in R/3?
II) In ECS - Did you use the scenario were a SC is transferred to a PO in SRM and a STO in R/3?
Here are more detail of whate i have done:
A. In the Classic Scenario
I) Standard Purchse Order (this one works fine):-
I adapted the BADI BBP_CREATE_PO_BACK as follows :
1. Changing the document from EC to NB,
2. Changing the Vendor from 1000000272 to 1000000271,
Run the program - CLEAN_REQREQ_UP.
The system as expected - A PO is created and
In the Follow-on Document, in the SC, I get tow messages:
1. Shopping Cart 1000000508/1 Follow-on Document Created
2. Purchase Order 4400002238/1
II) Stock transport Order (here the problem arises):-
In order to create a STO
I adapted the BADI BBP_CREATE_PO_BACK as follows :
1. Changing the document type from EC to UB (STO),
2. Changing the Vendor to a Supplying Plant 236 (The central warehouse),
3. Changing the Item category 7 (U - Transport),
Run the program - CLEAN_REQREQ_UP.
A STO is created (Number 4400002239) but the number of the PO is not in
the SC.
In the Follow-on Document in the SC I get only onr tow message:
1. Shopping Cart 1000000511/1 Follow-on Document Created
To confirm the goods receipt of that STO from the status screen I get the messsge: 'PO 1 contains no items for confirmation'.
When confirming the goods receipt from the Confirm Goods/Service I get the message: 'PO 4400002239 contains no items for confirmation'.
B. In the Extended Classic Scenario
I adapted the BADI BBP_ECS_PO_OUT_BADI as follows :
Document type - UB (STO),
Supplying Plant 1000 (The central warehouse),
Item category 7 (U - Transport),
The BADI use the BAPI BAPI_PO_CREATE1.
The BAPI_PO_CREATE1 returns the following listed error messages:
'Net price must be greater than 0'.
Because the BAPI is activated whith extra parameters like: Invoice Receipt Indicator and Partial Invoice
Your help is appreciated.
Rgds
Yoram

Plant replication issue in SRM

Hi Experts,
We replicated around 70 plants from ECC to SRM.Each plant coressponds to unique company code only.
The only similarity in all the plants is the adress details.
After replication,faced the red error for about 5 plants out of the 70 stating "Location Already Exists, Partner: 00100025XX Plant: 1090 System: DE1XXXXXXX The Plant is a Duplicate in the same System Plant: 36XX".
I maintained the Search term field in the adress details of those 5 plants and then replicated them from ECC to SRM.Those 5 plants got replicated succesfully.This was in Development environment.
In quality system when i try to replicate the plants,am facing the same red error for 50 out of the 70 plants.
I have checked in table BBP_LOCMAP and i find no entries related to plants which are said to be duplicate.
Please advise.
Thanks in advance
Supriya

Hello,
Please find all of the information on plant replication and maintenance
below.
Firstly, see the note:
563180 Locations - Replication of R/3 plants
1. BBP_LOCATIONS_GET_ALL should be run once in your system.
This cannot be scheduled as a report.
2. For further replication of plants, please use
BBP_LOCATIONS_GET_SELECTED.
3. The reason for the error BBP_LOCATION004 is due to duplicate
address data for plants. The system will check all address fields and
look for duplicates, if any are found the system will issue this
message and the plant will not be replicated.
4. Once replicated plant address data etc should be maintained using
the browser transaction 'Manage Business Partners' BBPMAININT.
Please set this transaction up as a browser transaction
for the SRM admin user.
5. Plants can also be created in SRM using this transaction BBPMAININT.
The can be assigned to R/3 plants.
See note 563108:
"You can also create individual locations via the Web transaction
'Managing Business Partners' and assign them to an R/3 plant."
Hope this information clarifies your issue.
Kind Regards,
Edel.

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

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

Currency issue in Local PO in SRM ( SRM 4.0, Ext. Classic scenario)

Hello SRM community,
       There is contract exist at a Product category level which is created in currency Euro & can be used by both local as well as well global purchasing org. for subsequent PO releases( Call off).
We are using extended classic scenario, SRM 4.0. before explaining the scenario, here is what we have maintain for a vendor in BBPMAININT
Let say..
Vendor(Business Partner)             Purchasing org.                     Currency
100168                                         Global Purchasing org.     Euro
100168               Local Purchasing Org                SEK
Now there are two scenarios in this
Scenario No.1
When Strategic purchaser directly creates any purchase order release for Local purchasing org. with reference to above created contract
& if he chooses Euro as a currency, system throws a warning message as "Currency Euro in Purchase order is different then the PO currency SEK of vendor.
but still he manage to order the PO Euro.
Scenario No.2
If strategic purchaser creates shopping cart for local purchasing org. where S/C currency is Euro & assign above contract as a source of supply.
Local PO gets created but the system swaps the currency in PO automatically to SEK which is nothing but the currency available for Vendor/Pur. Org combination
in BBPMAININT.
Why there is this difference in behaviour.
I mean, when you directly creates a PO release wrt contract, system allows you to select currency other then the one maintain in BBPMAININT for Vendor/PUr.Org combination however if you try to create a SC for Local pur. org with contract as a valid source of supply then system overrides the SC currency with the currency maintain in the BBPMAININT for Vendor/PUr.Org combination
We would like to know if there is any way possible by which we can maintain SC currency in PO & should not allow system to
swap it with what is being maintain in Vendor/Pur.Org combination in BBPMAININT.-
is there any Badi available where we can change this behaviour..& if poosible a way of approach to do it through Badi....
Any help is well appreciated with full rewards to valuable suggesation.
Regards
Bharat Morajkar

Hi Bharat,
You can use the BADI <b>BBP_DOC_CHANGE_BADI</b> to make changes to the document, after user entry and before saving the document to the database.
BBP_SC_CHANGE method can be used for changing shopping carts.
Hope this works in your case. Try it and let me know.
Rgds,
Teja

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

Conversion of classic scenario into extended classic

hai,
i have configured classic scenario.now i wanted to convert classic into extended classic.what are all the things i need to do?do i need to close all of my shopping carts?do i need to implement any badi?what are all the modifications i have to do in organization structure and attributes?do i run any reports for extended classic scenario?could any one help me to find out the solution.
thanks and regards
chakradhar

Hello Chakradhar,
These pointers will help.
A. Activate the extended classic scenario
SRM: Sap Implementation Guide  Supplier Relationship Management SRM Server  Cross-Application Basic Settings  Activate Extended Classic Scenario
B. Activate IPC pricing
C. BAdIs relevant for the pricing are activated correctly BBP_PRICEDATA_READ; PRODUCT_UPDATE2
D. SRM-SRM server-Technical basic settings-Define backend system for product categeries- SRM system as target system
E. Number Ranges
Check your business requirements, one of the good idea will be to switch the extended classic scenario only for a particular set of categories need ECS. you can have both scenarios,with deciding factor as product category.
Thanks
Ashutosh

Contracts in Classic Scenario

In Classic Scenario SRM 5.0 with ECC 6.0, how can I create an ECC Contract with a requirement from the Purchaser's Worklist ? Do I use the Global Outline Agreement? If so, what are the config steps ? Full points assured. Thx.
Raja

Hi You can create a GOA in SRM and distribute a contracts in Backend .
Basic configuration
(1) Define a transaction type GCTR
(2) No range internally in EBP and Externally in R/3,
(3) Idoc settings sending to r/3 like BLAORD, COND_A
(4) You must have a role to create a GOA as SAP_BBP_STAL_STRAT_PUR-
CHASER.
(5) You may need to map all condition type in SRM and R/3.
(6) Refer this notes 646903 - Global outline agreement: Tips and tricks
You can refer some related links...
http://help.sap.com/saphelp_srm50/helpdata/en/42/f93dfd975f3ee6e10000000a1553f7/frameset.htm
http://help.sap.com/saphelp_srm30/helpdata/en/7d/0a093f7c392e5ae10000000a114084/content.htm
Re: SRM GOA [BLAREL ]
regards
Muthu

Consignment process in Classic scenario

HI Experts,
can anyone let me know whether we can use consignment process in classic scenario.
we are having SRM 5.0
If it is possible kindly let me know what needs to be done in SRM to set up the same
regards
subbu

Hi Subbhu
Azad is correct.
but you can see this thread but doing enhancement you might achieved .but before comitting to customer you have to do lot of business analysis /business impactsand etc.
See Yorum thread. you must get an idea.
STO classic scenario SRM 4.0
BBP_CREATE_BE_PO_NEW badi helps
you need to change the item category /document type must have consignment
Consignment is items procured on a consignment basis.
Material number is necessary
Account assignments cannot be made for material ordered on consignment.
Goods Receipt is necessary
Invoice receipt not necessary
Consignment stocks are managed separately and are not valuated
br
muthu

Urgent ! Purchase Requisition not created in Backend Classic Scenario

Hello All,
I am implementing the classic scenario SRM 5.5. We have replicated the material form the backend to SRM system. Also we have made the necessary config such as maintain backend system, Define Backend System for Product Category, Define Number Ranges for Shopping Carts and Follow-on Document, Define Number Ranges per Backend System for Follow-on Document. Now the problem i am facing is that in the dev system SC with line item with desc and the product (material replicated from backend) as line items are created and their PR is created in the backend. However the same is not happening in the QA system. Only those SC with line item as Desc/text only are created in the backend and those having have product id dont transfer to create PR in the backend. There is no message in the RZ20, SM13, ST22, SM21 etc. Alsowhen i try to tranfer it using the FM BBP_PD_SC_TRANSFER it is created successfully and there is entry in BBP_DOCUMENT_TAB which is cleared afetr clean_reqreq_up is run. I am not sure whats is going wrong. Please help me out guys.
Thanks
Karthik

Hi Andy,
Thanks for the quick responses. I dont see any PR doc no and neither the BUS object type in BBP_PD item details. Please see the o/p below
BE_LOG_SYSTEM                R3QAS400
BE_OBJ_ITEM
BE_OBJECT_TYPE
BE_OBJECT_ID
BE_REFOBJ_TYPE
BE_REFOBJ
BE_REFOBJ_ITEM
BE_REFOBJ_SBITM
BE_REFOBJ_TYPE2
BE_REFOBJ2
BE_REFOBJ_ITEM2
BE_REFOBJ_FYEAR2             0000
BE_STGE_LOC
BE_PLANT                     IE01
BE_BATCH
BE_VAL_TYPE
BE_MOVE_REAS                 0000
BE_EXPERYDATE                000000
BE_PUR_GROUP                 440
BE_PUR_ORG                   IE01
BE_CO_CODE                   IE01
BE_DOC_TYPE                  EC
BE_ACCREQUIRED
BE_SP_STK_IND
BE_INFO_REC
BE_MOVE_TYPE                 101, so i am not sure what could be going wrong.
Is there any way i can debug it and find out what the cause is,
though the calls to the bapis are asynchronous. Also just for the reference sake my backend is 46C. I have been grazing through the notes but haven't found a substantial one.

Contract preference over PIR in SOS in Classic Scenario

Dear all,
We are in Classic Scenario, SRM 4.0 (SRM Server 5.0) SP9 with R/3 4.6C backend
When a Material has a contract and a PIR in the backend, if the material is added from catalog in the Shopping Cart, both Purchase Info Record and backend Contract are found as Source of Supply and then apparently no priority exist then no automatic Source of Supply is defined (user must select one to have one assigned).
At the opposite doing the same in ME51N in backend selects contract automaticaly (when Sourcing determination is flagged).
What we want is that if a Contract and a PIR are found for the material in the SC then the contract is taken automatically as preferred Source of Supply like in ME51N.
Any idea? Is that a bug? Or what can we change? BADI?
Thanks a lot
RD

It is possible to disregard inforecords for sourcing purposes in R/3. If you do so EBP will automatically disregard inforecords as well. This approach consistently removes info-records as sources of supply in both, R/3 and EBP. here's how:
1. run cmod transaction in R/3 and create your project
2. Assign enhancement LMEQR001 to your project
3. In component EXIT_SAPLMEQR_001 there is include
ZXM06U52 and you need to enter some code in this include. Here is an example how to remove ALL inforecords:
INCLUDE ZXM06U52 *
loop at t_sources.
if not t_sources-infnr is initial.
delete t_sources index sy-tabix.
endif.
endloop.
Note: BBP_SOS_BADI can only be used for customizing the searches of local sources of supply: local contracts, vendor lists and or vendor interlinkages

SRM 7 : Vendor record replication in backend with Extended Classic Scenario

Hello,
We are implementing SRM 7 with Extended Classic Scenario and Supplier Self-registration.
Can you explain what is to be configured to get the new vendors replicated to the backend?
Thanks in advance.

Hi,
It is possible to transfer suppliers to ERP system, if you use 'Supplier registration with ERP' scenario. After registration and acceptance, newly registered suppliers would appear on supplier monitor from where you can transfer them to backend system.
Check the below link for more details:
http://help.sap.com/saphelp_srm50/helpdata/en/cf/35074152aff323e10000000a155106/frameset.htm
Regards,
Sanjeev

Plant Replication Classic Scenario SRM 3.0

Similar Messages

Maybe you are looking for