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

Similar Messages

No accts maintained for company code clearing between comp.cds RTIL and RCP

Dear sir
i am stock transfer in one plant ot another plant on 301MVT use in MB1B t code that time below error is showing
No accts maintained for company code clearing between comp.cds RTIL and RCPL.

Hi,Since you are doing 301 for plants in 2 different company codes you need to maintain CC clearing account,it will not required if do this scenario in same company code, Maintain the Company code Clearing account between 2 company codes through transaction OBYA with proper GL account.

No accts maintained for company code clearing between comp.cds 1000 and 000

Dear all,
I am doing STO between company codes with UB doc type, and I am getting error as " No accts maintained for company code clearing between comp.cds 1000 and 0001."
how to resolve this. plz give steps?
Regards,
Prashanth

Hi...
AS per me OBYA is the Transaction code to maintain account
determination for Cross company code Transactions.
Plz go ahed & confirm.
S..tosh.

No accts maintained for company code clearing between comp.cds 8490 and 062

Hi,
Error when iam doing the PGI:
No accts maintained for company code clearing between comp.cds 8490 and 0627.
What settins are missings. This delivery is normal delivery only.

Hi,
If you are doing intercompany transaction then you need to assign GL accounts in tcode OBYA.

PGI-No Accounts maintained for company code clearing between company codes

Dear Expetrs,
When i am doing PGI getting error that is no accts maintained for company code clearing between 0010 to 0035. This is intercompany process. In our intercompany company codes is 0010 and 0020. So we maintained already clearing acconuts between 0010 and 0020 in OBYA. But when am doing post goods issue... getting error no accts maintained between 0010 to 0035. Actually here supposed to take clearing accts between 0010 to 0020. I couldnt understand why its taking 0010 to 0035. Could you please suggest me where i did mistake, Please suggest me ASAP.
Tanks & Regards,
VS

Dear Lakshmipathi,
Here am pasted the OBYA Screen...whatever i maintain pls check and suggest me. i am suspecting on Debit posting kes and credit posting keys maintain as 01 and 31 is corect.
Transaction          BUV   Clearing between company codes
Posted in             0016
Cleared against       0013
Debit posting key    01                  Credit posting key   31
Account debit        7790000013          Account credit       7720000013
Posted in             0013
Cleared against       0016
Debit posting key    01                  Credit posting key   31
Account debit        7790000016          Account credit       7720000016
Thanks & Regards,
Vasu

No accts maintained for company code clearing between comp.cds

Hi All,
I have the following issue when trying to carry out inventory clearing using LI21.
When I carry this out for Plant B all is OK.
When I try it for Plant 'A' I get the following error.
No accts maintained for company code clearing between comp.cds A and B.
When I clear inventory from plant A why would the system look at plant B?
This does not occur when clearing from plant 'B'.
I am convinced it must be a WM setup issue, but could be FI.
I am not a WM guy but need to resolve this issue.
Thanks
Stuart

In LI21 system will pick up the quantity from storage type 999.
It will clear this storage type and tie up the WM-IM stock for a particular plant.
This error message which u have mentioned usually comes when u are doing a stock transfer between 2 plants in different company codes.
system looks for a GL account in transaction type BUV in tcode OBYA.
Check this setting also .

How to display COMPANY CODE DESCRIPTION ON THE TOP LEFT OF PAGE

How to display COMPANY CODE DESCRIPTION(Field BUTXT) ON THE TOP LEFT OF EVERY PAGE OF THE REPORT GENERATED.
Actually I have collected BUTXT using
'select butxt into table itab from t001 where bukrs = p_bukrs'
where p_bukrs is the selection screen field.
REQUIREMENT: Depending on what company code we give on the selection screen, corresponding company code description(butxt) should be displayed at the top left of every page. how would i display it in TOP-OF-PAGE EVENT.

Hi
It's very simple, but what is the need to use into table itab in your select query.
Rather, define a variable
data: v_butxt type t001-butxt.
Select butxt into v_butxt from t001 where bukrs = pbukrs.
TOP-OF-PAGE.
write :/ v_butxt.
Regards
Surya.

There is a tax code difference between PO and MIRO

There is a tax code difference Between PO and MIRO.tax code is VO in PO but it must be T8 becuase invoice is T8.can you please solve this issue ?
Thanks & Regards
Raj

Hi
Put the Tax code same in PO and MIRO, because In F-47 you have to give the PO no in it. Then create MIGO, Then F-48 and then create MIRO, and Then F-54 Then F-58.
Thanks
Anil

Synching the data between MDM and ECC

Hi All,
We have been on SAP MDM Central Master Data Management scenario for more then a year now. In the pas we have seen many issues ike - Syndication server failures, idoc failures due to which the data is not 100% in synch between MDM and ECC.
Though we are working on the idoc failure tracking process but my question is this -
I need to create an automated program which runs on a weekly basis finds the data which is out of synch in MDM and FEP and gives me the same. So the logic should be something like this - Pick up the records updated during the last week in MDM, look for those records in ECC. Compare field by field and give me the delta.
Since it is a central master data management scenario hence there are cases in which records are created in MDM but not present in ECC may be because of syndication failures or idoc failures.
Any one worked n a similar sort of program/logic? Kindly let me know your experiences as well in efforts to keep the data in synch.
Regards,
Indraveer

Hello Indraveer
Yes you can do it.
You can configure exchange between ECC and MDM by schedule directly or through PI
or
SAP MDM 7.1 has own API for ABAP, JAVA, .NET. (5.5 for ABAP,JAVA, .COM)
That may be abap transaction or java(.net) application is working by schedule.
more about MDM API you can read here:
ABAP
http://help.sap.com/saphelp_nwmdm71/helpdata/en/48/edff445128209ce10000000a42189d/frameset.htm
JAVA and .NET
http://help.sap.com/saphelp_nwmdm71/helpdata/en/13/041975d8ce4d4287d5205816ea955a/frameset.htm
JavaDocs
http://help.sap.com/javadocs/MDM71/index.html
Regards
Kanstantsin Chernichenka

Any SAP Note for RFC Error between BI and ECC 5.0

Hi..
the RFC Destination between BI and ECC 5.0 is giving errors.
Plz let me know if there is any Support pack or any solution to fix this error.
thanks..

Hi,
pls find the RFC connection details
1 Prerequisites
1.1 User Roles
Use
With the Building Block Connectivity a configuration role for each component is provided to access all transactions relevant for the installation. The following roles are available:
Technical name Description File name for upload
B02_01C B02 - Connectivity Configuration Role (SAP R/3) B02_01C.SAP
B02_03C B02 - Connectivity Configuration Role (SAP BW) B02_03C.SAP
C71_04C B02 - Connectivity Configuration Role (SAP CRM) C71_04C.SAP
B02_04C_SRM B02 - Connectivity Configuration Role (SAP SRM) B02_04C_SRM.SAP
Procedure
Please upload the necessary roles and add them to your user, using transactions PFCG (Role Maintenance).
2 Local Settings
This chapter describes all local settings that are necessary for each component like SAP R/3, SAP SCM, SAP BW, SAP CRM or SAP SRM.
2.1 SAP R/3
2.1.1 Define Client Administration (SAP R/3)
Use
This activity allows you to change Customizing settings.
Prerequisites
You have logged on to the system in English in order to start with the installation of the Best Practices Scenario.
Procedure
Run the following activity:
SAP R/3 Role Menu Define Client Administration (SAP R/3)
Transaction Code SCC4
SAP R/3 Menu Tools  Administration  Administration  Client Administration  Client Maintenance
Then carry out the following steps:
1. Choose Display  Change.
2. Confirm the warning message Caution: The table is cross client.
3. Select your SAP R/3 client and choose Details.
4. In the Change View Clients: Details screen, activate the following settings:
u2022 Automatic recording of changes
u2022 Changes to Repository and cross-client Customizing allowed
u2022 eCATT and CATT allowed.
5. Save.
6. Go back to the SAP Easy Access menu.
2.1.2 Defining a Logical System for SAP R/3 (SAP R/3)
Use
The purpose of this activity is to create a logical system for your SAP R/3 System. To enable communication between systems within your system landscape, you must
1. Define the systems as logical systems.
2. Assign the logical system for the SAP R/3 System to a client.
This enables the systems to recognize the target system as an RFC destination. If the logical system has already been created, skip this activity.
Logical systems are defined cross-client.
Procedure
Carry out the following steps:
1. Access the transaction using:
SAP R/3 Role Menu Defining a Logical System for SAP R/3 (SAP R/3)
Transaction Code SPRO
SAP R/3
IMG Menu Basis Components (for R/3 Enterprisse: SAP Web Application Server)  Application Link Enabling (ALE)  Sending and Receiving Systems  Logical systems  Define Logical System
2. Choose New entries.
3. In the column Log System, enter a name for the logical system that you want to create.
4. In the column Name, enter a description of the logical system.
Log. System Name
where XXX is the system name
and NNN is the client.
5. Save your entries.
A transport request for Workbench appears.
6. Select an existing request or create a new request, if necessary.
A transport request for Customizing appears.
7. Select an existing request or create a new request, if necessary.
2.1.3 Assigning Logical System to Client
Use
The purpose of this activity is to make an assignment for the logical system. Skip this activity if a logical system is already assigned to your client.
Procedure
Carry out the following steps:
1. Access the transaction using:
SAP R/3 Role Menu Assign Logical System to Client
Transaction Code SCC4
SAP R/3 Menu Tools  Administration  Administration  Client Administration  Client Maintenance
2. Choose Display ® Change.
3. Confirm the warning message The table is cross client.
4. Select your R/3 client and choose Details.
5. Enter the name of the logical system of your SAP R/3 client.
6. Save and confirm the warning message Be careful when changing the logical system.
7. Choose Back twice.
2.1.4 Creating an RFC User (SAP R/3)
Use
To enable communication between the SAP R/3 back-end system and the SAP SCM System, you have to create an RFC user in the SAP R/3 System.
The RFC user in the application client enables multiple RFC connections. Skip this activity if an RFC User has already been created.
Procedure
Carry out the following steps:
1. Access the transaction using:
SAP R/3 Role Menu Creating an RFC User (SAP R/3)
Transaction Code SU01
SAP R/3 Menu Tools  Administration  User Maintenance  Users
2. In the User field, enter RFCUSER.
3. Choose Create.
4. On the Maintain User screen, enter the following data on the Tab entry screens:
Address
Last Name
Function
Logon data
User type System
Password LOGIN
Profile
Profiles SAP_ALL
SAP_NEW
S_BI-WX_RFC
Defaults
Logon Language EN
5. Save your entries.
2.3 SAP BW
2.3.1 Define Client Administration
Use
This activity defines changes and transports of the client-dependent and client-independent objects.
Procedure
1. To perform this activity, choose one of the following navigation options:
SAP BW Role Menu Local Settings ® Define Client Administration
Transaction Code SCC4
SAP BW Menu Tools  Administration  Administration  Client Administration  Client Maintenance
2. Switch to change mode.
3. Select your client.
4. Choose details.
5. In field Currency enter the ISO-code of the local currency, e.g. USD or EUR.
6. In field Client Role enter Customizing
7. Check the settings for changes and transport of client-specific objects and client-independent object changes
If you want to use the settings made by BC-Sets or manually in other systems (other than BW), u201CAutomatic recording of changesu201D and u201CChanges to Repository object and cross-client Customizing allowedu201D is required.
Result
Client administration has been defined to support the installation using Best Practices.
2.3.2 Defining a Logical System for SAP BW (SAP BW)
Use
In this step, you define the logical systems in your distributed system.
Prerequisites
Logical systems are defined cross-client. Therefore cross-client customizing must be allowed in your client (this can be checked in transaction SCC4).
Procedure
To carry out the activity, choose one of the following navigation options:
SAP BW Role Menu Defining a Logical System for SAP BW (SAP BW)
Transaction Code SPRO
IMG Menu SAP Reference IMG  SAP Customizing Implementation Guide  SAP NetWeaver  Business Information Warehouse  Links to other Systems  General Connection Settings  Define Logical System
1. A dialog box informs you that the table is cross-client. Choose Continue.
2. On the Change View u201CLogical Systemsu201D: Overview screen, choose New entries.
3. On the New Entries: Overview of Added Entries screen enter the following data:
Field name Description R/O/C User action and values Note
Log. System Technical Name of the Logical System Enter a name for the logical BW system that you want to create
Name Textual Description of the Logical System Enter a clear description for the logical BW system
4. Choose Save.
If a transport request for workbench and customizing is displayed choose existing requests or create new requests.
If you want to continue with the next activity, do not leave the transaction.
Result
You have created a Logical System Name for your SAP BW client.
2.3.3 Assigning Logical System to Client (SAP BW)
Procedure
To carry out the activity, choose one of the following navigation options:
SAP BW
Role Menu Assigning Logical System to Client (SAP BW)
Transaction Code SCC4
SAP BW Menu Tools  Administration  Administration  Client Administration  Client Maintenance
1. In the view Display View "Clients": Overview, choose Display.  Change
2. Confirm the message.
3. Select your BW client.
4. Choose Details.
5. In the view Change View "Clients": Details, insert your BW system in the Logical system field, for example, BS7CLNT100.
6. Save the entries and go back.
2.3.4 Opening Administrator Workbench
Procedure
To carry out the activity, choose one of the following navigation options
SAP BW Modeling  Administrator Workbench: Modeling
Transaction Code RSA1
1. In the Replicate Metadata dialog box, choose Only Activate.
2. If a message appears that you are only authorized to work in client ... (Brain 009) refer to SAP Note 316923 (do not import the support package, but use the description under section Workaround).
2.3.5 Creating an RFC-User (SAP BW)
Procedure
To carry out the activity, choose one of the following navigation options:
SAP BW Role Menu Creating RFC User
Transaction Code SU01
SAP BW Menu Tools  Administration  User Maintenance  Users
Then carry out the following steps:
1. On the User Maintenance: Initial Screen screen:
a. Enter the following data:
Field Entry
User RFCUSER
b. Choose Create.
2. On the Maintain User screen:
a. Choose the Address tab.
b. Enter the following data:
Field Entry
Last Name RFCUSER
Function Default-User for RFC connection
c. Choose the Logon data tab.
d. Enter the following data:
Field Entry
Password LOGIN
User type System
e. Choose the Profiles tab.
f. Enter the following data:
Field Entry
Profiles SAP_ALL , SAP_NEW and S_BI-WHM_RFC
g. Choose Save.
Do not change the password of this user as it is used in RFC connections.
2.3.6 Define RFC-USER as default (SAP BW)
Procedure
To carry out the activity, choose one of the following navigation options
SAP BW Role Menu Define RFC-USER as default (SAP BW)
Transaction Code RSA1
SAP BW Menu Modeling  Administrator Workbench: Modeling
1. On the Administrator Workbench: Modeling screen choose Settings  Global Settings.
2. In the Global Settings/Customizing dialog box choose Glob. Settings.
3. On the Display View u201CRSADMINA Maintenance Viewu201D: Details screen:
a. Choose Display  Change.
b. Enter RFCUSER in the BW User ALE field.
c. Choose Save.
Hope this helps in solving u r problem
Regards
Ramakrishna Kamurthy

Difference between classic and ECC pca

Hi All,
Could someone please tell me what is the difference between Classic and ECC PCA?
Regards
Suresh

Hi
Enhancement of new general ledger flexibility, that is you can enter user-defined fields and update the corresponding totals (Profit Center / Segment / Region). Many standard reports can evaluate the information from the user-defined fields.
Due to the new document splitting function (Online Split) you can create financial statements, if required, at the company code level as well as for entities, such as the Profit centers / Segment.
Using the u201CDocument splittingu201D function (online document split), you can create balance sheets for company codes as well as for further entities such as the profit center . The balance is then set to 0 for each document for the profit center.
There are no longer any time-consuming reconciliation tasks between FI and CO for the end of period, since in real-time in Controlling, the system transfers cross entity processes into the new general ledger.
Transactions 3KEH and 3KEI from the classic Profit Center Accounting for maintaining proposal profit centers for balance sheet and P&L accounts are no longer used to set the profit center.
Display of receivables and payable's per profit center real time ( if document splitting is active).
Detailed information for the setting the Profit Center accounting in the New General Ledger:
Define the update of the characteristics u201CProfit Centeru201D and u201CPartner Profit Centeru201D in the ledger by selecting the scenario u201CProfit center updateu201D.
Define the field u201CProfit centeru201D as a splitting characteristic in the document splitting.
Set the u201CZero balanceu201D indicator again for the added field u201CProfit centeru201D and you therefore have to create balance sheets on the profit center.
Activate the required entry field check to ensure that the profit center is set in all postings.
EC-PCA Profit Center Accounting u2013 Profit center accounting forms an interface between the operative controlling (CO) applications and the Enterprise Controlling (EC) module It reflects the actual and plan postings from operative controlling and settlements components with which it is in targeted in real-time. It then summarizes this data according to profit centers, which reflect the internal structure of areas of responsibility within the company code
Regards
Edited by: Dublin on Oct 26, 2009 12:17 PM

SNP planned order availability date difference between APO and ECC

Hi,
I have observed that SNP Planned order availability date is not matching between APO and ECC. Details are as follows.
I ran SNP Optimizer with bucket offset of 0.5. After publishing the optimizer created planned orders to ECC, only start date is matching.
Example:
I am using PDS as a source of supply.
Fixed production activity in SNP PDS is 1 day.
GR processing time: 3 day
After running optimizer planned order is created with dates explained below.
Start date/time: 09.05.2011 00:00:00
End date/time: 12.05.2011 23:59:59
Availability date: 16.05.2011 00:00:00
Because of bucket offset defined as 0.5 optimizer planned order availability is start of next monday.
After publishing this planned order to ECC dates on the planned order is as follows.
Start date: 09.05.2011
End date: 09.05.2011
Availability date: 12.05.2011
I have not maintained any scheduling margin key in ECC. Also if I dont define the GR processing time, planned dates between APO and ECC always match. Can anyone explain the impact of GR time on the availability date.
Regards,
Venkat

Hi Venkadesh,
What's "state stamp"? Do you mean different time zone?
note : 645597 mentioned by Nandha is very helpful:
In standard, CCR will use duedate - "the available date of the output product".
Nandha's words "In SAP APO, if the receipt date of the primary product deviates from the
end date of the last activity of the order, the receipt date
always identifies this as inconsistent. You cannot rectify
inconsistencies of this type by using CCR."
I guess in your PDS or PPM, the output product is not assigned to the End of the last activity. Someone changed it?
Please CIF the PDS or PPM again.
If you really want to apply a note, please use note 815509 as you're using planned order,
and system will use order end date in CCR instead.
GR time is always considered. BR/Tiemin

G/L account determination in SRM by company code

Hi,
We have a requirement to default G/L account not only by product category but also by company code. I can see the field company on the BBP_DET_ACCOUNT table but in configuration this field is not there. I know the field company is not directly the company code field in ECC but is the BP in the org plan that has the company code flag on the function tab.
We also know that we can use the BADI BBP_DETERMINE_ACCT to accomplish what we want but I am trying to find a way of doing it without any development.
We are in SRM 5.5 connected to ECC 6.0.
Thanks and regards, Jose Oyon.

Dear Olyn,
if it is showing in Account Determination analysis that "G/L account has been determined", but still in the incompletion log it shows "G/L account was not determined", then the most possible chance is that after creating the Sales Order the G/L account was determined for Customer or Material.
You can be able to save the order even it is incomplete.
Solution: you can delete the line item from the sales order & again add it
Please let me know if this solution helps you or not.
Thanks
Bidhu

How to build search help for company code (BUK) in SRM

Hello,
I am new to SRM and was wondering if any have come across similar requirement. I am a workflow developer and we are building a custom table to derive deadline escalation timelines. We are also adding a field in our custom table for company code so that we can have company specific deadlines. table T001 is empty in SRM and hence we are unable to use F4 (search help). Is there existing functionality in SRM that gets this search from the backend ECC system and displays when F4 is pressed. How can I use that functinoality?
Appreciate any info folks.
Thanks again.
Samir

Hi
Which SRM version are you using ?
Related links ->
Re: Search Help on SRM front end screen
F4 Help for WBS Element
Re: Company Code defaults
Re: Search help for Custom Item level field
Custom field in SRM as a dropdown field with values stored in R/3
Calendar help for Date i/p field in SRM 5.0 shopping cart
Company code
Problems assigning values via F4 or search help
Also There is a standard table in SRM which contains Plant data ->
BBP_LOCMAP (Mapping Table Business Partner --> System --> Location)
Try creating a custom search help based on this Table, defined as selection method and assign the same to the related field.
Do let me know.
Regards
- Atul

Adding a new company code in the SRM Org Plan

Hi.
We have a requirement to create a new set of Company Code and Purchasing Orgs in SRM to reflect a recent new setup in our back end R/3 system. These are totally different legal entities and have to remain seperate to existing company code and puchase org.
When I go into SRM Org Plan and create a new Company Code, it is picking up the attributes from an already existing company code and incorrectly inheriting field values such as Company Code (BUKS etc).
Please can somebody explain if in SRM Org Plan (PPOMA_BBP) how I can create an additional Company Code without it inheriting anything from one that already exists.
Many thanks. David.

Dave
It soulnds like you've got your attributes maintained at the Root level of your org structure as opposed to the company level.
You really need to have an org that looks like this...
Root
|--- Company Code 1000 (Attributes for CC 1000 maintained here)
|--- Company Code 2000 (Attributes for CC 2000 maintained here)
Hope this helps
Regards
Keith

SRM-Synching company code description between SRM and ECC

Similar Messages

Maybe you are looking for