Trading Partner Configuration in Production System

Dear All,
We are planning to implement trading partner in the production system.
The scenarios were tested in qulaity but i haven faced any errors,
I would like to know the risk of implementing Trading Partner in a live system.
Thanks and regards
Praveen Jagadeesan

Hi,
have you know what is the concept of Trding partner, how it will deriv in sap.
"In Business Terms Trading partner is your business partner within Group with whom you are doing business.In order to identify Inter Company transactions Trading partner field is used. You need to define all the Group Companies as company in SAP and all the defined Companies will be available for selection in Trading partner field. Trading partner can be defaulted in GL, Customer or Vendor Master. If you need you can populate trading partner at Document level too by doing settings in Document Type Master in T Code OBA7.
Trading partner is normally used to control (payment/transaction) vendor/customer business with the group. Something like group/inter group business. You have to go to master record. for eg, in customer master, go to CONTROL DATA tab so see Acccount Control, in which you have provide trading partner number/reference"
Regards,
Upendra.

Similar Messages

Oracle B2B 10g Remote Trading Partner Configuration

Hi All,
How to create a Business Action in operational capabilities of remote trading partner for the exchange of custom xml document betwenn trading partners.
Also please suggest any document where we can follow the steps for creating trading partner for custom xml exchange.
Regards,
Jagadesh.

You may like to refer -
http://www.b2bgurus.com/2007/12/how-to-handle-hosttrading-partner-with.html
Multiple "HOST-partner" configuration possible?
Regards,
Anuj

Trading Partner Configuration from FICA site

Dear Gurus,
We are struggling to bring the Trading Partner ID on FB03 or FBL3N screen after SAP ISU Invoice posting ? Please suggest necessary configuration or User Exit / Enhancement required for this.
Thanks In Advance
With Regards,
Sunil

Hi Sunil,
Trading partner can be inherited or derived from master or can be entered manually in transactions.
Updation of trading partner is being controlled through relevant document type configuration in SAP
Its being controlled through two main check boxes in document type configuration (transaction code-OBA7) namely, "Inter-company postings" and "Enter Trading partner" check boxes
a) If "Inter-company postings" check box is set and "Enter Trading partner" is not set
Functionality: Trading partner is derived from master data and no manual entry is possible in line item / transactions. Here trading partner must not be unique in a document.
b) If "Inter-company postings" check box is not set and "Enter Trading partner" is set
Functionality: Trading partner can be manually entered in line item / transaction by choosing Extras menu button -> Trading partner which will be applicable for all the line items in a document. Here trading partner is unique in the document.
c) If both "Inter-company postings" and "Enter Trading partner" check boxes are set
Functionality: Trading partners are derived from master data and can also be entered manually in the line item / transaction in the "More Data" screen. Here trading partner must not be unique in a document.
d) If both "Inter-company postings" and "Enter Trading partner" check boxes are not set
Functionality: Trading partner can be manually entered in a line item / transaction by choosing Extras menu button -> Trading partner which will be applicable for all the line items in a document. Here trading partner is unique in the document.
In short, both options (b) and (d) represents the same functionality and it depends on each of the document type configuration with the business process involved.
Hope it helps...
Thanks,
Amlan

Migrating Trading Partner from test to Production environment

Hi,
My Production environment has configuration for two trading partner.
I need to migrate one more trading partner from test environment to (the existing) production environment.
I see Agreement level export, TP level export, Config level export options in Oracle B2B.
Can you please suggests as to which is the fastest and most accurate way to migrate new trading partner configuration?
Regards,
Ravi Shah

There is nothing as preferred option. However you can keep few things in mind.
1. Agreement Export - Preferred option , if you would like to export only specific Trading Partner and Agreement details.
2. Repository Export - For full repository export.
3. Trading Partner Export - This option do not keep any TP in mind while taking the export, hence you may not information about Delivery channel and Agreement. This provides information about Trading partner profiles and Supported Document defition of the trading partner.
Let me know.

Validation for Profit Center and Trading Partner

Hi Gurus,
Please help me in creating validation for Profit Center and Trading Partner.
I want system to give an error if we use Trading Partner related to particular profit centers.
Please revert asap.
Thank You

Hello,
Please use T.code OB28 and select the call up point 2.
Than go to Prerequisite in expert mode and say
Prerequisite : BSEG-VBUND <> ' '
Check: BSEG-PRCTR = ' '
Error Message.: xyz
I have created Validation understanding if someone gives Trading Partner and also Profit center while posting a doc than it will generate an error message.
however if you have some diff req please change it accordingly/ take Abapers helps if not very clear.
I hope this helps
Regards
Shireesh

Trading Partner Import

Does anybody has dealt with Trading Partner conversion from Legacy systems?
I want to know what are the Pros and cons of the process.

Hi,
In Case of 10g using oracle wallet manager import trusted trading partner certificate.
In case of AS11G use the below command to import the trading partner certificate into jks,
keytool -importcert -file -keypass
Please also look into the below link for more details,
http://blogs.oracle.com/oracleb2bgurus/2009/08/certificate_management_in_11g.html
Regards
Nandagopal

Trading Partner Config

Hello everyone,
I am looking for Trading Partner configuration Steps for intercompany clearing. I will appriciate if some one can share the important steps.
Thanks in Advance
Krishna

You Can Assign Trading Partner in OBY6
At Customers and Vendors
Have you done IC config?
Regards,
Vivek

COM_HIERARCHY_DELETE_ALL in Productive system

Hi CRM experts,
We need to run the report COM_HIERARCHY_DELETE_ALL in the Production CRM System, but when we try to execute this report, the system issues a message to archive the data first.
However we have executed the same report in the Quality Assurance and Development system sucessfully.
Does anybody know how to configure the Productive system to not issue this check / message?
Thanks in advance
Monalisa

Hi Monalisa,
As far as my knowledge goes, you can only be able to delete the product hierarchy in the same system in which you have created. Looks like you had transported the product hierarchy either from dev or test system.
Did you try to delete a single node using 'COM_HIERARCHY_DELETE_SINGLE' ? What was the outcome?
Reward if helps
Regards,
Paul Kondaveeti

Configuring ALE Logical Systems and Partner Profiles

hi,
Trying to build a scenario which deals with two third party systems transfering XML file from one to another. Sender is using a file adapter. Reciever is using an Idoc adapter. However the pre-requisite mentioned for this exercise are that ALE logical systems and partner profiles must be configured (these steps are not outlined in the exercise) . Could i get help on what steps i need to carry out for sender/reciever to configure logical systems and partner profiles.
regards,
Manpreet

Hi Manpreet
At the R/3 system the partner profile should be maintained for both the third parties.
for creating the partner profile go to transaction we20, give the
partner number :your logical system name or customer number or vendor no
partner type:LS(logical system)or ku(customer)OR LI(vendor)
give the message type in the outbound parameters
after this double click on the message type and give the login deatils for the RFC destination define the port and all
if you still have problem please reply back
Thanks
Rinku

Steps to configure BPM report from Solman 7.00 for productive system ECC6.0

Hi all,
Please given me the steps to configure Buisness process Monitoring reports from Solman 7.0 for productive system( ECC6.0, windows & database oracle 10.2),
I wanted to create the Reports of monitoring the buisness.
Regards,
Akash Basis consultant.

Thanks for replying Volker von Gloeden,
This thread is my first one in SDN & I am very glad that someone has given the answer ,
I will take a look for solution you have provided & will inform you.
Thanks again.

Transport ALE Configuration from Development to Production System

Hello All,
We have created ALE-IDOC scenario in the development system and its working fine. Now we want to transport it to the Production / Quality system. How can we transport the settings like logical systems, port definition, partner profiles, distribution model , RFC destinations from one system to another system??
Because the client numbers are different for development , quality and production systems.. Do we need to transport the logical system and client assignment using STMS or create directly in the target system??
Thanx in advance...

The issue with transporting the ALE distribution model is that the source and target logical system names change between the dev, test and prod environments.
Assume an ECC6 and PI landscape with dev/test/prod called E6D/E6T/E6P and PID/PIT/PIP with all systems using client 100. By default (SAP recommendation) the logical system name for E6D client 100 is E6DCLNT100 and its PI partner in the dev landscape will be PID client 100 with logical system name PIDCLNT100. In test the logical system names will be E6TCLNT100 and PITCLNT100 and in prod E6PCLNT100/PIPCLNT100.
So, when a distribution model is set up in dev with a source system of E6DCLNT100 sending messages to a target system PIDCLNT100 everything works nicely. This assumes that the PIDCLNT100 logical system partner in WE20/WE21 is mapped to a port which maps to an RFC destination pointing to client 100 of PID.
When this model is transported to the test system it won't work because the logical system names are wrong.
It is possible to create a logical system name called PISERVER in SALE and then map that, via WE20/WE21 to point to the corresponding PI instance. Thus in E6D, WE21 would map logical system PISERVER to the RFC destination for PIDCLNT100 but in E6T the mapping would link to RFC destination PITCLNT100 and in E6P to PIPCLNT100. In this way any ABAP programming trying to use the ALE distribution model would send messages to PISERVER and would be transportable.
However, setting up the source system in the same way appears to be impossible. When attempting to generate partner profiles, transaction BD82 stubbornly insists that the source system for which it will build profiles MUST be the logical system name defined for the execution client in SCC4. Theoretically, mapping similar to that for PISERVER could be performed for ECC6SERVER and the ALE distribution model could be built to send messages from ECC6SERVER to PISERVER but BD82 won't honour this source system.
This appears to make it impossible to transport an ALE Distribution Model. Can anybody provide a process to overcome this apparent architectural limitation?

Create a Support Message in Production system showing up in Solution Manage

Has anyone setup the link between creating a support message (under help) in a production system (like ECC) and SAP's Solution Manager.
I understand that it uses BADI SBCOS001 with the interface method PREPARE_FEEDBACK_BO, but when I try to run it, it tells me that Customizing for feedback functionality missing. What functionality is missing? And how to I correct this? And how do I ensure it shows in SAP Solution Manager under a solution or project?
Thanks
Paul

Hi Paul
The only way is to use the IMG. I have just completed this via the IMG info. BUT, it is not that simple.
Make sure your RFC's are trusted and that you have SAP ALL during config.
I hope this will help:
Setup Service Desk
Steps to follow while configuring support desk.
1) Implement the note 903587 .
2) Create all the relevant RFC objects in the satellite system and add the appropriate logical components using transaction SMSY.
3) Check all the objects in the table BCOS_CUST using transaction SM30.
Appl : OSS_MSG
+ :W
DEST :BACK RFC NAME (for solution manager system keep this field as 'NONE')
+ :CUST 620
+ :1.0.
*4) Check whether the BC sets are activated or not using the transaction SCPR20.If the BC sets are not activated then implement the note 898614.The steps to activate the BC sets are described below
4.1) Activate SOLMAN40_SDESK_BASICFUNC_000 BC Set.
4.2) Activate this in expert mode with option u201COverwrite everythingu201D.
4.3) Activation of the following components has to be done by replicating the previous steps
3.1) SOLMAN40_SDESK_TPI_ACT_AST_001
3.2) SOLMAN40_SDESK_ACTIONLOG_001
3.3) SOLMAN40_SDESK_ACT_ADVCLOSE_001
3.4) SOLMAN40_SDESK_TEXTTYPES_001
*Depends upon the number of inactive BC set objects that we have after the upgrade.
4.4) if the actions mentioned in 4.3 are not listed while executing the transaction SCPR20, then implement the note 898614.In the source client 000 of the solution manager system create a transport request using transaction SE09, unpack the file 'PIECELIST_SERVICE_DESK_INIT.ZIP' from the attachment of the note. Copy the contents of the file 'PIECELIST_SERVICE_DESK_INITIAL.TXT' to the transport request. And activate the actions. Use transaction SCC1 to import the transport request to the solution manager client. If any short dump occurs during the activation, implement the note 939116.
5) Check whether the number range is set correctly. If not set the number ranges of basic notification (ABA) and the support desk message (Service transaction SLFN).To be able to use the same number ranges for both message types, the internal number range for basic notification (ABA) must correspond to the external number range for the support desk message.
Number ranges for ABA notifications
5.1) create an internal and external number range using transaction DNO_NOTIF.
5.2) assign number range intervals to groups internal and external.
5.3) SLF1 is the internal number range group
5.4) SLF2 and SLF3 is the external number range interval
5.5) Use transaction DNO_CUST01 to assign message categories to the number range.
5.51) Go to transaction DNO_CUST01
5.52) From the GOTO menu select the menu item DETAILS
5.53) Now you can assign the number range of basis notification (ABA) into the notification type.
The number range for ABA notification is 12 characters in length and to make it compatible with the CRM service transaction insert 2 ZEROES at the beginning.
Number ranges for Support Desk notification
5.54) Use transaction CRMC_NR_RA_SERVICE, and define the internal and external number ranges. Intervals must correspond to the intervals of the basic notifications (ABA notification).
5.6) Then assign both the external and internal numbering
5.61) Go to SPRO and then to SAP Solution Manager
5.62) Then select General Settings and then select Transaction types
5.63) Select the transaction type SLFN and then select the menu item DETAILS from the GOTO menu.
5.64) In the Transaction Numbering block, assign the internal and external number range. The Number Range object should be CRM_SERVIC.
5.7) To view the priorities use transaction DNO_CUST01 and select the notification type as SLF1 and then select priorities from the left pane of the screen. The priorities of the first four cannot be deleted, but new priorities can be added.
6) Check the Action profiles for ABA Notifications (Action profiles are used for synchronization of ABA notification with the CRM Service transaction).
6.1) To check the action profiles use the transaction SPPFCADM and select the application type DNO_NOTIF then select u2018DEFINE ACTION PROFILE AND ACTIONSu2019.
6.2) Select the item u2018SLFN0001_STANDARD_DNOu2019 and then from the menu GOTO, select the menu item DETAILS.
7) The Action profile u2018SLFN0001_STANDARD_DNOu2019 has to be assigned to the message category SLF1 (ABA notifications) using the transaction DNO_CUST01.
8) The action profile for the support desk message can be set to u2018SLFN0001_ADVANCEDu2019.
8.1) From SPRO select SAP Solution Manager then Scenario Specific Settings.
8.2) Select the item Service Desk and then to general settings.
8.3) Execute the category u2018Define Transaction Typesu2019.
8.4) Select the transaction type as SLFN
8.5) From the GOTO menu select the menu item u2018DETAILSu2019 and assign the action profile as SLFN0001_ADVANCED .
9) Activate the partner/ Organization
9.1) Go to CRM->MASTER DATA->BUSINESS PARTNER->INTEGRATION BUSINESS PARTNER ORGANIZATION MANAGEMENT->SET UP INTEGRATION WITH ORGANIZATIONAL MANAGEMENT.
9.2)Find the entries starting with HRALX
HRALX-HRAC WITH VALUE 'X'.
HRALX-OBPON WITH VALUE 'ON'.
HRALX-PBPON u2018ONu2019.
HRALX-MSGRE u2013 u20180u2019.
9.3) If entries are not found create it.
10) Generate Business partner screens
10.1) Go to transaction BUSP.
10.2) Execute the report with the following parameters
CLIENT - Client in which business partners should be created (solution manager client)
APPLICATION OBJECT-
SCREEN - *
Generate all/ selected screens - All screens.
delete sub screen containers -
11) implement SAP note 450640.
11.1) Go to transaction SA38 and select the report CRM_MKTBP_ZCACL_UPDATE_30.
11.2) Execute it with test mode box unchecked.
If a new relationship is to be created then steps 12 and 13 has to be followed
12) To create a relationship category
12.1) Go to transaction BUBA
12.2) Select the entry CRMH00: Undefined relationship
12.3) click on copy
12.4) Rename CRMH00 to ZCRMH00.
12.5) CREATE A RELATIONSHIP CATEGORY.
IN GENERAL DATA FILL LIKE ' FROM BP1 : HAS THE ACTIVITY GROUP '.
' FROM BP2 : IS A PART OF ATTUNE
13) Add the relationship category to the support team partner function
13.1)Use SPRO
IMG GUIDE->SAP SOLUTION MANAGER->SCENARIO SPECIFIC SETTINGS->
-> SERVICE DESK->PARTNER DETERMINATION PROCEDURE->DEFINE PARTNER FUNCTION.
13.2) FIND THE PARTNER FUNCTION SLFN0003 (SUPPORT TEAM).
13.3) In the field relation ship category, Select the newly created relationship category and save.
14) Steps 12 and 13 should be repeated for various business partner types like sold-to-party, message processors if new relationship is to be created for the respective business partner types.
15) Create a new access sequence for the support team determination
15.1) Go to the following IMG Path: SAP Solution Manager Implementation Guide ->
SAP Solution Manager -> Configuration ->
-> Scenario Specific Settings ->Service Desk -> Partner Determination Procedure ->
->Define Access Sequence
15.2) Click on New Entries
15.3) Define a new access sequence with sequence name as u2018Z001u2019 and description u2018NEW BP RELATIONSHIP ACTIVITY GROUPu2019
15.4) Create an new Individual Access with the following value:
u2022 Batch Seq: 10
u2022 Dialog Seq : 10
u2022 Source : Business Partner Relationship.
u2022 Detail on the source:
u2022 Partner Function : Reported By (CRM)
u2022 Mapping/restrictions
u2022 Flag Mapping/definition for partner being Searched
u2022 Partner Function in Source: Support Team (CRM).
Save it.
This Access Sequence will give us the Partner which has the relationship assigned
to the Support Team in the Reported By partner data.
16) Adapt the partner determination schema/Function
16.1) Go to the following IMG Path: SAP Solution Manager Implementation Guide ->
SAP Solution Manager -> Scenario Specific Settings ->Service Desk ->
-> Partner Determination Procedure -> Define Partner Determination Procedure.
16.2) The two options to adapt partner determination schema are
16.21) Adapt the standard Procedure (SLFN0001) or to create a new one by copying the standard one.
16.22) select the line starting with SLFN0001 or the newly created procedure.
16.23) Double Click on Partner Function in Procedure.
16.24) Select the Partner Function "Support Team", and click Details.
16.25) in the detail view only change the Partner Determination/access Sequence to
the one we've just created. Save your entry.
17) Create a root organizational model.
17.1) Go to the following IMG Path: SAP Solution Manager Implementation Guide -> SAP Solution Manager -> Configuration-> Scenario Specific Settings ->Service Desk -> Organizational Model ->Create a Root Unit for Your Organizational Structure.
17.2) creating an organizational unit by entering the data in the BASIC DATA tab.
17.3) enter the organizational unit, the description and save it.
18) Create the support team organization
18.1) go to the following IMG Path: SAP Solution Manager Implementation Guide -> SAP Solution Manager -> Scenario Specific Settings ->Service Desk -> Create Organizational Objects in the Organizational Structure. Or use transaction (PPOMA_CRM).
19) Create the business Partners.
19. 1) Key users- End user (Business Partner General) ,Address should be specified.
19.2) go to the transaction BP.
19.3) create a new Person, Select the role: Business Partner (Gen).
For Identification of the key user
19.31) click on the identification tab
19.32) enter a line in the identification number formatted as follows
IDTYPE : CRM001.
Identification number : <SID><INSTALL NUMBERS><CLIENT><USERNAME>
eg: USER NAME : USER1.
CLIENT : 100.
SID : ER1.
INSTALL NUMBER : 123456789.
IDENTIFICATION NUMBER : ER1 123456789 100 USER1.
20) Message Processors- Support Team members .
20.1) they should be created first as the users in the corresponding client of the solution manager.
20.2) As business partners they will have the role 'EMPLOYEE'.
20.3) Go to transaction BP .
20.4) Create New Person with the role employee.
20.5) In the Identification tab you should enter the user name in the employee data/User Name.
eg: username: proc1
enter proc1 in the field User name.
21) Organizational Business Partner- Organizational BPS have the same country in there main address tab. They should be created through the organizational model. Business partner corresponding to the root organization have the role 'SOLD TO PARTY'.
22) Assign the business partners (Message Processors) to the previously created support team.
22.1) Go to transaction PPOMA_CRM.
22.2) Select the support team 1.
22.3) Click on create
22.4) select position
22.5) call it 'MPROC_T1/Message Processors for team 1
22.6) Replicate it for the other support teams.
22.7) Select the position MPROC_T1/Message Processors for team1 and click assign,
choose owner/Business Partner find and select the business partner
22.8) Validate and Save it.
22.9) If the assignment of business partner is not possible then implement the note 1008656
Or 997009
23) Create the iBase component
23.1) IMG Path: SAP Solution Manager Implementation Guide -> SAP Solution Manager -> Basic Settings -> Standard Configuration of Basic Settings -> Solution Manager -> iBase -> Initially Create and Assign the Component Systems as iBase Components.
23.2) or use the transaction IB51 to create the installed base.
23.3) it is also possible to create the SOLUTION_MANAGER, select the solution and go to menu Edit -> Initial Data Transfer for iBase.
24)Assign Business Partners to iBase Components
IMG Path: SAP Solution Manager Implementation Guide -> SAP Solution Manager -> Basic Settings
-> SAP Solution Manager System ->ServiceDesk-> iBase -> Assign Business Partners to iBase Components.
*--optional--
If you want to be able to assign the System Administrator: Go to the IMG: SAP Solution Manager Implementation Guide -> Customer Relationship Management -> Basic Function -> Partner Processing -> Define Partner Determination Procedure.
Select the entry "00000032 Installed Base/IBase" and double click on Partner Functions in Procedure.
Then copy the Entry "Contact Person (CRM)" to a new entry with the partner Function "System Administrator (CRM)" , save it.
Go back to transaction IB52, select a component, and Goto -> Partner, you should be able
now to assign the partner Function "System Administrator".
25) Assign the SAP Standard Role to the user. Message Creator should have the role : SAP_SUPPDESK_PROCESS.
26)Define the transaction variant for the message processors
Go to the following IMG Path: SAP Solution Manager Implementation Guide -> SAP Solution Manager -> Configuration -> Scenario Specific Settings ->Service Desk -> General Settings -> Specify User Selection Variant.
Here we will create variants for the central message processing transaction CRM_DNO_MONITOR.so that the user will have direct access to there dedicated message.
27) Go to transaction PFCG
27.1) Enter the role name as Z_MSG_PROCESSORS and choose single role.
27.2) Give a description Message Processor role and save it.
27.3) Go to the menu tab and choose add report
27.4) select the report type : ABAP Report
27.5) And in the report enter the report name as 'CRM_DNO_SERVICE_MONITOR'.
27.6) Enter the previously created variant.
27.7) flag the skip initial screen box.
27.8) flag the SAPGUI for windows.
27.9) Create a new transaction with tcode starting with Y or Z.
27.10)Display this transaction and check the values at the bottom of the screen
in the subscreen Default Values, you should have the following parameters:
u2022 D_SREPOVARI-REPORT = CRM_DNO_SERVICE_MONITOR
u2022 D_SREPOVARI-VARIANT = MY_TEAM_MSG
u2022 D_SREPOVARI-NOSELSCRN = X
And also all the user should have the correct role.

IDoc Configuration for Production Order Creation and Change

Hi All,
Please Help me out for IDoc Configuration for Production Order Creation and Change
I have found the IDoc for Production Order
Messgae Type : LOIPRO and IDoc type : LOIPRO01
Actually my requirment is to send the (LOIPRO01 )IDoc from SAP R/3 to XI system ,when ever the Production Order Created and Changed,
I have done following Configurations:
1. RFC Destination created for XI system
2. PORT was created for XI
3. Partner profile created WE20 and LOIPRO01 IDoc is added in OutBound Perameter.
I need to know how to do the followning.
1. How do i configure the outbound Production order idocs when Production Order is created or changed.
2. in NACE (Output control) which is the Application for Production Order.
3. How can I set IDoc as output Type for Production Order Creation.
Thanks in advance
Dhanabal T

Hi Michal,
I know that it is the old thread but still want to get clarified from you out of curiosity.
Unlike other IDOC, i actiavated change pointers for LOIPRO
1.message and idoc type is linked
2.function module , message type , idoc type is linked
function module used is CLOI_MASTERIDOC_CREATE_LOIPRO
3.BD64, distribution model is created and distributed
4. port and partner profile is in place.
5. IDOC is not getting generated after creating the process order.
do we need to activate the change documents for the message type in BD52,
if yes can you please provide the object types for the same.
or i am missing something else. please guide me in this regards.
Thanks in advance for your time.
S.Janagar

Unable to update Partner Unit in Eccs with Trading Partner from FI

Hi,
I had removed the Breakdown category from the FS item Master (CX14) for a reco Acct by mistake .Now when i update the master table in CX14 with the same Break down Category(0110 - Partner Unit (break down Type-4) + Translation Currency (break down type -2)) the sytem than gives a pop up window showing the "Report for Transaction Check" where it asks for the Default Value of Partner Unit to be entered.Once i maintain the default value of partner unit all the document for the reco account gets updated with default Partner unit.However in FI module each of the documents posted for this account have diffrent Trading Partner due to which im unable to do the Interunit Elimination.
Kindly let me know how do i update Partner unit in all the documents in Consolidation with the trading Partner from FI module.
thanks
Karan

Once i maintain the default value of partner unit all the document for the reco account gets updated
this system behavior makes sense as you are trying to change configuration after loading transaction data. what happens if you go back to the underlying accounts and change TP back to what FI is showing? if u have to deal with a lot of documents u may want to set up a BDC session to do the mass update.

Using a Trading Partner Directory Implementation for Companies

Hello experts,
I am looking into configuring delegate useradmin using companies.
The UME approach requires a engine reboot and somhow doesnt fit our requirements.
The second approach - "Trading partner directory implementation" seems feasible.
To implement this do I need to have any additional Bussiness package or additional installation for my portal? The document does state that this approach is only available with SAP supplier relationship management. What does this mean??
thanks,
Vineeth

Hello Peng Ronan,
Did you have any success with your Trading Partner Directory?
Our project includes ECC, CRM 5.1, SRM6.0 and Portal7.0. We have this CRM scenario where a customer (manager) logs on and approves one of his employees, already self-registered, as a customer Portal user. UME seems to support that scenario, but it can only retrieve company information from a SRM backend system using a custom implementation of the Trading Partner Directory interface. In our case it is a CRM scenario and CRM Business Partners are not replicated on SRM.
What is that SRM Trading Partner Directory interface and how much effort is involved in this custom implementation?
Does the portal need to restart for new Companies to be added?
Is this only for EBP scenario?
Is there a better way to update the list of companies in UME from a list of CRM Business Partner?
Thanks

Trading Partner Configuration in Production System

Similar Messages

Maybe you are looking for