Company name in SRM and ECC

Hi,
Recently we have changed the company name in ECC system but this new name didn't reflect in SRM system. Upon investigation we found that system has already captured this name in table BBP_ATTR_VALUE_T.
Is there any standard program that needs to be run to refresh these entries from ECC?
Regards,
Alok

Hi,
Some attribut descriptions (like plant & company code) are read from R/3 and stored in SRM table BBP_ATTR_VALUE_T.
Try to delete those entries in SE16, for BBP_ATTR_VALUE_T with ATTR_ID = 'BUK'.
BR,
Disha.
Pls reward points for useful answers

Similar Messages

SRM-Synching company code description between SRM and ECC

Hi,
I have two questions:
1. Is company code descriptions and other details are stored in SRM (like T001 in ECC)?
2. If yes, how can we synch the company code description in SRM and ECC? What is the program name to synch both system
Jit

Sanjeev,
Thanks for the reply. But still there is description difference in SRM - frontend and backend system.
The SRM backend is correct but when we log ninto the SRM portal (frontend), the company code description are missing some characters. Can you pl let me know where is the frontend is picking the Company code description in SRM?
Jit

Mapping between SRM and ECC long text

Hi Experts,
Please advise if anyone know where SAP do mapping of long texts of SRM and ECC objects. I found it in one program in my last project but forgot the name.
Regards,
Kamal

Hello Kamal,
You can use BBP_LONGTEXT_BADI for mapping SRM text to ECC text. SRM needs mapping rules to map SRM text into ECC text.
For details check BBP_DPO_TO_BAPI_MAP that executes the mapping ( text_copy_rules_be_get ).
Hope this helps.
Thanks
Ashutosh

Can we use NWBC with both SRM and ECC

HI
Can we use NWBC both SRM and ECC . or do i have to use EP .
Thanks,
Pooja

Hi
Hope this will answer your question
ECC Transactions in NWBC Browser SRM 7.0
Thanks,
Ashish

Link between SRM and ECC invoice

Dear gurus,
I need to find the link between SRM and ECC invoice number, can you please provide me the related tables?
Thank you in advance for your collaboration.
Regards,
Fuffo

i don't have access to the system now but i guess will be table BBP_PDBEI.
or you can go tcode BBP_PD, check in item level.
cheers.

SRM AND ECC

Dear all,
Iam new to SRM.pls explain brief about SRM.
I have installed ECC 6.0 ABAP STACK only hp-ux,db2 9.1.
pls tell me 1.whether we need to install abap+java stack in srm or only java is enough.
2.pls tell me brief explanation about how to go about that.
3.how to link srm and ecc 6.0.whether srm

Dear Rajesh,
SRM is a e-procurement solution and it's web based procurement. If you are having MM knowledge then you can understand very easily or Even if you knew sap-abap then you can understand quickly SAP-SRM.
Please go thorugh the below link then you can understand very easily.
http://help.sap.com/saphelp_srm50/helpdata/en/8d/f6a93e08503614e10000000a114084/frameset.htm
If you require more clarifications then let me know.
Thanks
Ravi

Unit of Measurement is comming **** in SRM and ecc system

Hi All,
I create new Unit in CUNI and replicated in my system but now if i see all the old PO's in SRM and ECC.....All units of measurement are comming '****' in place of unit of measurement but when i create a new Sc and PO replicated in ECc that vlaue is comming perfectly fine . Please tell me how i can fix this bug.
Regards to all,
Smriti Arora

i check translation it is availabe in english.But how could this happen to all the UOM.......i check in ECC and SRM ie coming ****.
Smriti Arora

Logical systems assignment when SRM and ECC are on 2 different servers

Hi SRM guru's,
What is the standard practice for Logical system creation and assignment when ECC and SRM are on 2 different servers.
I could not able to find which i created a logical system in SRM server which i created in ECC
Same for the ECC also.
how do i assign logical system of SRM to ECC
vice versa.
your prompt response is appreciated.
Regards

Hi Sai,
Logical System Naming/Creation procedure is not dependent on the servers but it is just a logical representation of a system.
As you are trying to name logical systems for ECC & SRM, please follow the below procedure which is usually recommeded by SAP and followed.
Logical System : <SID>CLNT<Client Number>
For Example if you have a client 300 in system DE0 (also called SID), the logical system name will be DE0CLNT300. And it will be same for SRM system.
You can refer the below document which eplains the creation of logical system and RFC destinations etc
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFAALEQS/CABFAALEQS.pdf
Note: Only while configuring the RFC Destination, the servers will play a crucial role.
Regards
Kathirvel

SRM and ECC integration

Hi Gurus,
We are in a phase of integrating SRM with ECC, so that any master data created in ECC should be replicated in SRM etc...
Can any one provide me detail step by step configuration required to integrate SRM with ECC?
Any material witll be helpful.

Hi sanju,
see these links
https://www.sdn.sap.com/irj/sdn/articles-community?prtmode=print&startindex=261 - 38k
https://www.sdn.sap.com/irj/sdn/articles?startindex=21 - 46k
www.sap-press.com/product.cfm?account=&product=H2900 - 34k
thanks
karthik
reward me idf usefull

SRRELROLES TABLE COMPARISION BETWEEN SRM AND ECC

Hi all
i would like to compare both tables SRRELROLES in ecc and srm for any one of SRM Business objects and linked ECC Business Objects for ALL the records not one records.
how .any clue is appreciated.
i followed peter methid but not works for me
the relations are stored in the tables SRRELROLES (this consist the documents) and BBP_PDBINREL (this consists the links):
In the table SRRELROLES are all of the the documents listed (SC, PO, BID...). Each line of the SRRELROLES consist a ROLEID. If you call the table BBP_PDBINREL with this roleid, as a result you will get the link (ROLEID_A or ROLEID_B) to the related documents.
Whit this ROLEID just call the table SRRELROLES and you will get the related document.
I tried in development box . it did not work. let me try other environment
Regards,
Peter
muthu

Sanjeev,
Thanks for the reply. But still there is description difference in SRM - frontend and backend system.
The SRM backend is correct but when we log ninto the SRM portal (frontend), the company code description are missing some characters. Can you pl let me know where is the frontend is picking the Company code description in SRM?
Jit

Vendor deletion in SRM and ECC

Experts,
We are on SRM 5.0.ECS.,
I have read several threads on SDN but none talks about the actual steps of setting the flag for deletion of a vendor in ECC and then updating the chnages in SRM.
What are the steps for setting the deletion flag for vendor in ECC??DOes it need to be done throigh XK06?
Also once the flag is set in ECC,are the changes replicated through UPDVD??Also wha are the updates done on SRM side for that vendor??Is the deletion flag also set for the vendor or the vendor is directly dleted from SMR?????If so which tarnsaction can I check that??
After the vendor deletion happen on both ECC and SRM,what is the message which comes up when we try to create PO with this vendor in SRM?
Also before the vendor is deleted from both systems,is it necessary to close all the old documents(SC and PO) which has this vendor?
Thanks.

Hi,
What are the steps for setting the deletion flag for vendor in ECC??DOes it need to be done throigh XK06?
Yes it can be done by that tcode.
Also once the flag is set in ECC,are the changes replicated through UPDVD??Also wha are the updates done on SRM side for that vendor??Is the deletion flag also set for the vendor or the vendor is directly dleted from SMR?????If so which tarnsaction can I check that??
tcode : BP (Tab Control )
You will see central block for that vendor. If purchasing block is setup it can be seen in manage business partner tcode.
After the vendor deletion happen on both ECC and SRM,what is the message which comes up when we try to create PO with this vendor in SRM?
If central block is there it won't be available in search list. If still user manages to enter the vendor the system may throw up error message. Vendor is blocked for purchasing.
Also before the vendor is deleted from both systems,is it necessary to close all the old documents(SC and PO) which has this vendor?
Vendor is treated as business partner in the SRM. BUPA_TEST_DELETE is used to delete any vendor or business partner. The system itself will issue an error message that vendor can't be deleted. In R/3 its independent.
My suggestion is apart from deletion please select purchasing block.

How to synchronise SRM and ECC for purchase groups?

HI,
recently we created two purchase groups in ECC. But these purchase groups did not replicate to SRM.
the table in ECC T024 has those purchase groups but the table in SRM HRT5500 does not have those purchase groups.
How can we make them in sync. Please guide me.
Thanks,
Nandan Upasani.

Hi,
Thatu2019s correct that you cannot establish to replicate Porg and pgrp to SRM. So better you perform following creation and assignment in SRM PPOMA_BBP Tcode as u2013
1.     Create purchasing group in SRM by copy any existing Pgrp and change the details as you created in ECC.
2.      You have to select a purchaser whom you are going to do purchasing assignment.
3.     Do the purchasing assignment to the purchaser's position.
You have to do this process for all the pgrps you added.
Regards,
Atul

PR to SRM and ECC

Hi Friends,
We are on SRM Server 5.5 with ECC 6.0 classic scenario. We have external requirements ( Purchase requisition in ECC) coming to SRM sourcing. In SRM we are creating GOA (Using SRM becuase of document builder) and distributing contract o backend ECC.
Material Group and Purchasing group are controlling the PR to pass to SRM.
Can we create a PO with same data of PR in ECC??? as well as SRM ( With similar data)???
As we are getting "Purchase requisition 10000601 00001 can only be ordered in system SRDCLNT301"!!!
Message no. 6Q202
Thanks in advance,
Vamsi.

Dear Nandu,
There's nothing to fear because when u know how it works ,than its simple.
when a PR to be transfer to SRM, then it need to insert into EPRTRANS table.
So here u can do :
1. You can set all mat group and purch group combination as per your requirement
if then in the future some PR' need to be process in R/3,then you clear the EPROFILE(you can make a small program to update it).
2.Then if somehow the management decide to bring to SRM again, you can then set the EPROILE again, then insert the PR and PR item to table EPRTRANS(make a small program also to insert this data), then run the program BBP_EQTREQ_TRANSFER to send the PR to SRM.
So no need any background job for this, you can give the tcode to clear the eprofile to the admin user,than if somehow they need to bring it to SRM again, you can help them..since this request will be very little.
I think that the message it sets in the program for PR with SRM profile, you may need a little modification for this.

Org Structre in SRM and ECC not in synch

Hi Friends
System :SRM 7.0 Extended Classic scenario.
Scenario: We never copied our Dev Client fro Production. Recently our Dev ECC system has been copied from Production
But ,because of memory constraints we cannot do the same to SRM system.
Also our Org is replicated from ECC to SRM.
Objective: 1 Need to synch up the Org of ECC (Dev) to SRM(Dev)
Query 1: How do we overwrite the entire org setup of SRM .
Query2 : Can we make use of concept of Plan version here so that we end up doing wrong ,so that we could switch back to
the earlier version)
(Any inputs on how can we make this possible)
Query 3: Is it possible to transport only the Org structure from either Production (SRM) or Develepoment (ECC).
While doing all this we have a major issue
Issue1: We could figure out that the number ranges setup in our Dev org structure of SRM are totally differnt from ECC Dev.
Ex: Postion number are 65XXXXXX in ECC where as 60XXXXXXX in SRM.
So when we perform PFAL ,it fails .
Any kind of inputs for us to brainstorm on this.
Regards
Sarath

Hi Sarath,
If we are using active version then change the number ranges in OONR against 01$$
Check the IDOC settings for message type HRMD_ABA. it must be transafer IDOC immediately.
Get the all active organization unit (O) from HRP1001 table in SAP and run PFAL in update mode for object (O) and let me know the result. It will replicate all orgnaization unit and position which fas assigned to above
Regards
Dayal

Tolerance in SRM and ECC (BE R/3)

Hi,
During posting of invoice in SRM, why only TOG tolerance will be used for checking tolerance?
As per my understanding, ECC tolerance will not be checked during SRM invoice posting.
Is it correct system functionality in SRM?
regards,
Rahul Mandale

Hi
Have you maintained the same configuartion data both in R/3 as well as SRM system for the Tolerance group ?
Which SRM scenario you have maintained ? Whci SRM System release you are using ?
I guess, ECC will be checked only based on the EBP Scenario yo have maintained for the system. But the BAPI call checks the configuartion data in SRM as well as R/3 before posting the Invoice.
Here is the detailed reasons behind the same ->
Set Tolerance Checks
In this activity, you define the tolerances for value or quantity overruns for deliveries, invoices, or order confirmations. Quantities or values of deliveries, invoices, or purchase order confirmations may vary up to these tolerance values. This allows deliveries or invoices to still be posted or data to be transferred from the order confirmation to the purchase order. For the definition of these tolerances, use tolerance groups to which you assign tolerance keys with different values and quantities. In this way, you can assign the same tolerances to different users.
Example
You assign the tolerance key DQ to the tolerance group M (manager), define an upper limit of 1000 for the value-based limit and activate the value limit. You also assign the tolerance key DQ to the tolerance group E (employee), define an upper limit of 100 for the value-based limit, however, and activate the value limit.
Standard settings
You can assign the tolerance group to a user group via the attribute TOG (tolerance group). For example, you assign the value M to user Manager 1 in the user attribute TOG for the user group Manager. If a user is logged on, the system always uses his TOG. If the user is not logged on, (BAPI is being used), the system uses the TOG of the vendor (business partner master record).
You can create tolerance groups by checking the quantity against the purchase order and the price (value) against the confirmation.
If you do not define any tolerances, this means that it is not possible to enter a delivery/incoming invoice in EBP where quantity or value has been exceeded.
The tolerance can be specified as a value, percentage, days, depending on the tolerance key. Two differently structured tolerances exist for value variances (DA for cumulated values, PP or PR for single values).
Percentage and absolute limits
If you define both a percentage and an absolute limit in a tolerance key, then you cannot post an invoice or automatically transfer data from the first purchase order confirmation received into the purchase order, if either one of the tolerances is exceeded. An absolute limit always has priority.
Example (with respect to invoice verification): You have defined a percentage upper limit of 5% and an absolute upper limit of 10. You wish to enter an invoice with the amount 1000, that exceeds the order value by 30. Although the percentage upper limit of 5% is observed, the absolute limit is not. The invoice exceeds the tolerance and can therefore not be posted.
Tolerances for deliveries/invoices
You can assign the following tolerance keys:
CF: Over/underdelivery in the confirmation
You use this tolerance to check how the confirmation deviates from percentage limits for overdelivery and underdelivery. First, the system checks in the confirmation against the tolerances created in the purchase order. If none exist, the system checks against the tolerances in the relevant tolerance group (for example, the tolerance group of the vendor). If you select the value Unlimited , no tolerances apply. The system displays a controllable message when a tolerance is not reached or is exceeded (see Influence Message Control).
DA: Exceed value (cumulated)
You use this tolerance both for confirmations and invoice entry. You can either define an actual value or a percentage for the upper limit. The system checks whether the cumulated invoice value (that is the value of all previous invoice documents + current invoice documents) exceeds the order value. The check is always made against the purchase order. If a confirmation is expected for an order item, a second tolerance check is made to determine whether the cumulated confirmation value (value of the previous confirmation documents + current confirmation) exceeds the order value.
DQ: Quantity variance (converted to currency amount)
You use this tolerance both for confirmations and invoice entry.
If a confirmation is expected for an order item and has already been posted, the system multiplies the net order price by (quantity invoiced - (total quantity delivered - total quantity invoiced)). If no confirmation is expected, the system multiplies the net order price by (quantity invoiced - (quantity ordered - total quantity invoiced)).
The system compares the outcome with the absolute upper and lower limits defined.
This allows relatively high quantity variances for invoice items for small amounts, but only small quantity variances for invoice items for larger amounts. You can also configure percentage limits for the quantity variance check. In this case, the system calculates the percentage variance from the expected quantity, irrespective of the order price, and compares the outcome with the percentage limits configured.
LA: Amount of limit purchase order
You use this tolerance both for confirmations and invoice entry.
The system calculates the sum of the value invoiced so far for the order item and the value of the current invoice and compares it with the value limit of the purchase order. It then compares the difference with the upper percentage and absolute tolerances defined.
LD: Limit purchase order; time limit exceeded
You use this tolerance both for confirmations and invoice entry.
The system determines the number of days by which the invoice is outside the planned time interval. If the posting date of the invoice is before the validity period, the system calculates the number of days between the posting date and the start of the validity period. If the posting date of the invoice is after the validity period, the system calculates the number of days between the posting date and the end of the validity period. The system compares the number of days with the absolute upper limit defined.
PP: Price variance (value variance from expected value)
You only use this tolerance for invoice entry.
The variance from the expected value is checked here, based on the preceding document (purchase order price or confirmation value).
The system determines by how much each invoice item varies from the product of quantity invoiced multiplied by the order price. It then compares the variance with the upper and lower limits defined (absolute limits and percentage limits).
TX: Tax variance
You use this tolerance exlusively for invoice entry. You define tolerances for tax amounts that are used with the tax calculation.
Tolerances for purchase order confirmations
SAP Enterprise Buyer uses the tolerances that you define here for the automatic data transfer from the purchase order confirmation to the purchase order and also for the manual data check in the vendor information. If the tolerances are exceeded, the system issues I messages.
You can assign the following tolerance keys:
PM: Quantity variance (converted to currency amount)
If a confirmation is expected for a purchase order item, the system calculates the purchase order confirmation net price multiplied by the purchase order confirmation quantity. The system compares this sum with the defined upper and lower limits. You can also define percentage limits for the quantity variance check. Then the percentage variance from the expected quantity calculated - independent of the purchase order price - and this is compared with the defined percentage limits.
PZ: Time overrun compared to purchase order
The system determines how many days the delivery date has exceeded the planned time interval by. If the delivery date of the purchase order confirmation is earlier than the delivery date of the purchase order, the system takes the purchase order date - the confirmation date; If the delivery date of the purchase order confirmation is later than the delivery date of the purchase order, the system takes the purchase order confirmation date - the purchase order date. The system compares the number of days with the defined absolute upper limit.
PR: Price variance (value variance from expected value)
Here the variance between the purchase order confirmation and the purchase order price is checked. The system determines for the items the price variance as the product of the quantity in the purchase order confirmation multiplied by the price in the purchase order confirmation, and it compares this variance with the defined percentage and absolute upper and lower limits.
Automatic transfer
Enterprise Buyer automatically takes the data from the first purchase order confirmation to be received, however, the following conditions apply:
Data transfer is only possible if no contract exists for the purchase order item.
All existing tolerances (quantity, price and delivery date) are adhered to and/or the purchase order confirmation data matches that of the purchase order exactly.
If the purchase order confirmation consists of multiple items, then the system transfers the data as follows:
The sum of all quantities
The highest available price
The latest available delivery date for materials or the maximum period for provision of services and limit items
( The system does not take any tolerances into account when data is transferred manually from the purchase order confirmation.)
The system does not automatically transfer any data from other purchase order confirmations. This prevents the original data of the purchase order being changed repeatedly by several purchase order confirmations one after the other when tolerances are exceeded.
Activities
1. Create a tolerance group and select it.
2. Assign one or more of the defined tolerance keys to the tolerance group.
3. Enter an upper and/or a lower limit. If you do not make an entry, the check is made against the value zero.
Further notes
The following table shows the existing assignment possibilities(X) for upper limits (UL) and lower limits (LL) :
Key Absolute Absolute Percentage Percentage Percentage Day Day
LL UL LL UL unlimited LL UL
CF X X X
DA X X
DQ; PM X X
LA X X
LD; PZ X X
PP; PR X X X X
Hope this will help.
Please reward suitable points.
Regards
- Atul

Company name in SRM and ECC

Similar Messages

Maybe you are looking for