ML81N Enhancement to trigger the 'Release Strategy'..very urgent !!

Hi Guys,
ML81N work in a manner such that if the net amount for any PO/Service entry is less than $2500 then its 'Release Strategy' tab is not active, because the minimum value should be 5000$ to trigger the 'Release Strategy'.
I have a requirement where i have to make that tab active and select the Lowest Release Strategy (the one for 5000$) even when the amount is less than $2500.
I have already tried with the ser exit EXIT_SAPLEBND_003, its a blank user exit and the structure available is CESSR.
Can any one tell me how to activate the 'Release Strategy' tab and the lowest Release stratedy should be selected ????
What i have investigated is that once i will set the Release Strategy to the lowest Release stratedy then that tab will automatically become active.
Please tell me how to select the lowest Release strategy using the CESSR structure ?
Points will be awarded...
Thanks
Rahul

Use this exit.
MM06E005

Similar Messages

User exit ML81N.....Name of user exit to trigger 'Release Strategy'..urgent

Hi Guys,
ML81N work in a manner such that if the net amount for any PO/Service entry is less than $2500 then its 'Release Strategy' tab is not active.
I have a requirement where i have to make that tab active and select the Lowest Release Strategy when the amount is less than $2500.
Can anyone please tell me the name of the user exit that controls the 'Release strategy'.
Points will be awarded...
Thanks
Rahul

Hi
Your settlement rule says "Settle to Cost Center" only.... I dont think any user exit can help in this case, if you want to settle occasioanlly to 2 cost objects
Try with these options
Option A
1. Remove the 100% validation tick in the settlement profile...
2. Maintain 2 settlement rules... i.e. One with Cost center and another with PSG... If any warning comes, ignore it
3. Execute settlement now
Option B
1. Maintain settlement rule with PSG as settlement receiver
2. In the same Settlement rule, Menu GO TO > DETAILS and maintain Cost Center also....
3. Now execute settlement...
Option C
1. Maintain settlement rule with PSG as settlement receiver
2. In the same Settlement rule, populate Cost Center also as a Valid Characteristic
3. Now execute settlement...
BR,Ajay M

Release strategy-- very very urgent

hi,
i have created the release strategy & its working properly in devolopment client. The entire thing is transported to quality client. But the characteristics values are not coming in the classification tab of release strategy. I have saved even the view in transport request but still the values are not coming. Can anyone suggest something. Its very urgent
thanks

Hi,
The transport of release procedure customizing data can only be done in
a restricted manner. Please take a look at attached Note 86900 and
follow the procedure described in this note, in order to correctly
transport your release strategies.
The classification data must be sent over using ALE. It does not
get transported directly. Notes 45951, 86900 and note 365604 should
help. Please follow the instructions in note 45951.
You can obtain information about how to set-up ALE in the Online
Documentation CD (R/3 Library -> CA - Cross Aplication Components ->
Business Framework Architecture -> ALE Integration Technology ->
ALE Quick start).
However, if you can't set-up ALE, you can re-create the classification
data agin in your target system.
For that you have to:
1. assign new values to the characteristic master data (trx. CT02)
2. assign the new data to the classification system (trx. CL30)
3. verify the consistency with trx. CL24. Please see note #186809.
For more information, please see note #365604.
There is another possibility that you could take into consideration for
the classification is to import them via batch input:
RCCTBI01 for creating characteristics
RCCLBi01 for creating classes
RCCLBI03 for classification
Regards,
Sunitha.

PO status if you change the release strategy procedure

What will happen to the half released PO/PRS if we change the release strategy?

Hi,
It won't Happen for Half release PO Document. The rerelase will get affect once the final release done or No release initiated to the document.
SAM

Source Determination resets the release strategy of the PR

Hi
I am trying to automate the Purchasing Cyle by running ME57 as a batch job along with ME59n for stock items on contract, however when I create the PR and approve it, when ME57 picks this approved PR it assigns the source automatically but removes the approval! I am having the ABAP consultants debug this, however is there something elementary that I have left out?
Regards
Thasmei Reddy

Check if u have release strategy based on vendor - FLIEF. This could be a reason. When u change the vendor or assign a vendor, the release strategy is getting reset .

Item category control the release strategy?

Hi,
Currently the purchase of a material needs to be released.
My issue is that as soon as I change the item category in the sales order,
the material does not need to be released.
How does item category control the release strategy?
Sincerely,
Ketan

Hi Ketan,
You can set item category in the characteristic of a release strategy.
In your case, I guess the item category characteristic is already created. So you can just add the desire value into the characteristic.
Go to SPRO > IMG > Material Management > Purchasing > Purchase Requisition > Release Procedure > Procedure With Classification > Set Up Procedure With Classification > Release Strategies
Select the related release strategy, double click to view the detail. You will see there are 4 buttons in the bottom of the screen. Choose 'Classification' and enter you value of item category.
Thanks & regards,
JT

Reset the Release Strategy of PO when Terms of Payment key is modified

Hi All,
Please let me know how to reset the Release Strategy of PO, whenever the Terms of Payment Key value id modified.
Thanks in advance.
Regards
Naveen

Hi,
This is not possible in SAP standard.
You have to use User Exit;
M06E0004 - Changes to communication structure for release purch. doc.
And Function Module;
EXIT_SAPLEBND_002 - Changes to Communication Structure for Release of Purchasing

How to set the Release Strategy without classification for PR

Hi,
I am able to set Release Strategy for PO with classification, however, now I want to set the Release Strategy for PR with classification. Can someone tell how to proceed to set the Release Strategy to PR with Account Assignment.
I crated the Release Codes, however not able to find what options to choose in the following steps :-
Release indicator
Assign Release Indicators
Release Points: Prerequisites
Determination of Release Strategy
Regards,
Yogesh

1. Release codes
 Create the release codes. For Purch. Officer, Manager and Sr. Manager
Like PO, MG, SM
2. Release indicators
 Define release indicators and branch to the detail screen. Here you
 define whether fixed purchase requisitions may be changed by Materials
 Planning, for example, and whether an RFQ or a purchase order may be
 created from the requisition.
 You can also determine the field selection here.
In the area "Changes after the start of the release procedure", you
 specify whether a requisition may be changed after the release
 procedure has begun. You specify whether the strategy has to be
 redetermined after changes, or whether the release procedure has to
 start all over again from the beginning.
This parameter bears a relation to the parameter "Value change". For
 example, previous releases are not cancelled if the value of the
 requisition item after the change does not exceed plus 10% of its
 original value.
Attention:
 Be sure to create a release indicator (e.g. B for "blocked") that
 serves as the starting point for subsequent indicators. Do not set the
 indicators for release for the issue of RFQs and PO on the detail
 screen for this indicator.
 Also create a release indicator characterizing the released status.
 Set the indicators for release for the issue of RFQs and PO on the
 detail screen.
You can use sytem defined indicator in this case you dont have to do anything
3. Assignment of release indicators
 Assign a release indicator in dependence on the status of the release.
Example:
 You create a release strategy S1 consisting of two release codes 01
 and 02. Release with 01 is a prerequisite for release with 02. If
 release has been effected with 01, the requisition has been given the
 "all clear" for the issue of RFQs.
 You have created the release indicators B (blocked), 1 (cleared for
 issue of RFQs) and 2 (cleared for RFQs and PO).
 Now enter the following as assignment:
Strategy C1 C2 C3 ...
 S1 B (blocked)
 S1 X 1 (RFQ)
 S1 X X 2 (RFQ/PO)
4. Release prerequisites
 Define which release codes are involved in a release strategy. Specify
 whether a code is set for a release status following release, and
 whether one release status is a prerequisite for another (+).
 Example:
Strategy Code C1 C2 C3 ...
S1 01 X
S1 02 + X
5. Determination of the release strategy
Determine the conditions under which each release strategy is
assigned. The criteria are account assignment category, material
group, plant, and value of the requisition item.
Here you can define the you criteria but one thing you keep in mind that you hae to define all criteria.
E.G if you will not define the Material group here but it will default in req in that case this will not work thats the reason you have to work with Classification.
In the classification whatever criteria you need that only you have to include like in your case you care about A/C category and value only.

Enhancement to Trigger the PO Release

Dear ABAPers,
I would like to trigger the PO release Function Module Whenever the Changes in PO.
Could you Please tell me which Enhancement Can be Used for this requirement.
Thanks & Regards,
Ashok.

Use this exit.
MM06E005

Trigger PO release strategy

How to retrigger PO release strategy after delete the items in ME22N?
It only be retrigger when we increase the price.
Any user exits dat retrigger the changes made?
Where is the user exits located?
Or any standard configuration need to be done.
I already set the Release indicator, changeable = 6, and % = 0.
I am using 470 version.
Please help to provide some solution.
Thanks.
Edited by: Elaine Tang on Jul 3, 2009 8:02 AM

Hi,
As for as I know, SAP has not provided the retrigger of PO release strategy if the Value of PO is decreased than the released PO price. It will only retrigger if PO price is increased than released one.
There is no User exit available for this, you can use the Version management usuage for any changes made in PO using the availble user exits.
There are lot of discussions done on this Retrigger of PO release strategy for any changes in PO -- but till now there is no positive result. Don't why SAP has not taken this issue very seriously.
If any others has found any solutions on this, let them share the information on this .
rgds
gsc

Getting Exception in the select clause - Very Urgent

Hi,
 I have given the below statement but it is showing the exception.
SELECT *
 FROM (lv_tab_name)
 INTO CORRESPONDING FIELDS OF TABLE <fs_1>.
If I execute the above select statement it is showing the below exception.
Exception CX_SY_NO_HANDLER triggered.
An exception with the type CX_SY_OPEN_SQL_DB occurred.
It is working very well if I mention the few field names.
Please let me know the possible reasons.
Thanks,
Suvin

Thanks much for your quick response.
I have tried with what you mentioned but it is not working.
Please find my code below.
*Declarations
DATA: ddfields TYPE STANDARD TABLE OF ddfield.
DATA: ls_ddfields TYPE ddfield.
DATA: lt TYPE lvc_t_fcat.
DATA: ls TYPE lvc_s_fcat.
DATA: lv_tab_name TYPE dd02l-tabname.
Data References
DATA: lt_data TYPE REF TO data.
DATA: new_line TYPE REF TO data.
Field Symbols
FIELD-SYMBOLS: <fs_1> TYPE ANY TABLE.
FIELD-SYMBOLS: <fs_data> TYPE REF TO data.
FIELD-SYMBOLS: <fs_2> TYPE ANY,
 <l_field> TYPE ANY.
Get the fields of the database table, here i am passing the table name
CALL FUNCTION 'DD_NAMETAB_TO_DDFIELDS'
 EXPORTING
KEYFIELDS = 'X'
NULLABLE = 'X'
 tabname = lv_tab_name
 TABLES
 ddfields = ddfields.
LOOP AT ddfields INTO ls_ddfields.
 ls-fieldname = ls_ddfields-fieldname.
 APPEND ls TO lt.
ENDLOOP.
*Assigning Field-Symbol to our dynamic internal table
ASSIGN lt_data TO <fs_data>.
Calling the method CREATE_DYNAMIC_TABLE
CALL METHOD cl_alv_table_create=>create_dynamic_table
 EXPORTING
 it_fieldcatalog = lt
 IMPORTING
 ep_table = <fs_data>
 EXCEPTIONS
 generate_subpool_dir_full = 1
 OTHERS = 2.
IF sy-subrc EQ 0.
 ASSIGN <fs_data>->* TO <fs_1>.
Create a work area for the dynamic table.
 CREATE DATA new_line LIKE LINE OF <fs_1>.
A field-symbol to access that work area
 ASSIGN new_line->* TO <fs_2>.
ENDIF.
Selecting the Data from the respective table.
SELECT *
 FROM (lv_tab_name)
 INTO CORRESPONDING FIELDS OF TABLE <fs_1>.
Please advise..it is very urgent.
Thanks,
Suvin

Logic for Refreshing the ALV Report (Very Urgent)

Hi Experts,
My ALV report needs a refresh button on the output.
The Refresh button should be available to allow user to keep this report on screen and refresh regularly rather than going back and running it again.
I am using Function modules and not OOPS Concept here.............As i am unaware of OOPS Please provide me solution in FM's Only.
Kindly send me sample logic for this, Very urgent if ur reply is helpfull.... u will be rewarded heavily.......................
THanks in advance.
Rajesh Kumar

Hi,
This mean to say that if you have a 'refresh' push button in your gui status, every time you press the button, the list should get refreshed.
In ALV, to refresh the table you have to call the method "refresh_table_display".
It has the syntax very similar to creating the table.
It has two parameters. In the first one, you can mention if you want to refresh only the data (the icons are not refreshed)
or
if you want to refresh only the icons around the grid (the data is not refreshed - this option is mostly not used in day to day applications).
the synatx is :-
call method grid (name of grid )->refresh_table_display
exporting
IS_STABLE = <STRUCT OF TYPE LVC_S_STBL> (THIS IS FOR DATA REFRESHING)
I_SOFT_REFRESH = <VARIABLE OF CHAR 01> (THIS IS FOR ICON REFRESHING).
Regards,
Bhaskar

Enhancement M06E0004 P.O. Release strategy

Hi ALL,
How to correct the below error message.
*********SAP log** tcode :OMGSCK
You must maintain a customer exit for characteristic Z_COSTCENTER
Diagnosis
You have linked the characteristic Z_COSTCENTER with field USRN1 of the communication structure CEKKO. In the standard system, this field is not populated. The data must therefor be determined in a customer exit.
Example
The person responsible for a cost center in a purchase requisition is to be determined. The name of this person is read from the cost center master record, placed in the field USRC1, and passed on to communication structure CEBAN.
The following customer exits are available to you:
Purchase requisition M06B0002
PO, RFQ, contract,
scheduling agreement M06E0004
Procedure
Check that you have maintained the relevant customer exit.
if any one has work on I_CEKKO this structure and used USRN1 field to validate some condition.
Please write me ..
Thanks ,
Shravan

Hi ALL,
How to correct the below error message.
*********SAP log** tcode :OMGSCK
You must maintain a customer exit for characteristic Z_COSTCENTER
Diagnosis
You have linked the characteristic Z_COSTCENTER with field USRN1 of the communication structure CEKKO. In the standard system, this field is not populated. The data must therefor be determined in a customer exit.
Example
The person responsible for a cost center in a purchase requisition is to be determined. The name of this person is read from the cost center master record, placed in the field USRC1, and passed on to communication structure CEBAN.
The following customer exits are available to you:
Purchase requisition M06B0002
PO, RFQ, contract,
scheduling agreement M06E0004
Procedure
Check that you have maintained the relevant customer exit.
if any one has work on I_CEKKO this structure and used USRN1 field to validate some condition.
Please write me ..
Thanks ,
Shravan

Controlfile has corrupted and not able to open up the database. Very urgent

Hi All,
I am working on 11gR1 database on linux environment and suddenly the DB went down. I look at the alert log and i am following that guidelines, but i am not able to put the database in mount state and it is thronging error message. Please suggest me in correct way. This is very high priority for me.
I have done below steps.
1.set the environment through . oraenv
2. export ORACLE_SID
3. SQL>startup nomount
ORACLE instance started.
Total System Global Area 4943876096 bytes
Fixed Size 2143944 bytes
Variable Size 2617248056 bytes
Database Buffers 2281701376 bytes
Redo Buffers 42782720 bytes
SQL>alter database mount;
alter database mount
ERROR at line 1:
ORA-00214: control file '/u02/oradata/beacondp/control02.ctl' version 390158 inconsistent with file '/u01/oradata/beacondp/control01.ctl' version 390097
4. SQL>alter system set control_files='/u02/oradata/beacondp/control03.ctl' scope=spfile;
System altered.
SQL>startup restrict
ORA-01081: cannot start already-running ORACLE - shut it down first
5. SQL>alter database mount;
alter database mount
ERROR at line 1:
ORA-00214: control file '/u02/oradata/beacondp/control02.ctl' version 390158 inconsistent with file '/u01/oradata/beacondp/control01.ctl' version 390097
alert log Information:
Thread 1 advanced to log sequence 9261
Current log# 3 seq# 9261 mem# 0: /u02/oradata/beacondp/redo03.log
Tue Sep 13 15:00:14 2011
********************* ATTENTION: ********************
The controlfile header block returned by the OS
has a sequence number that is too old.
The controlfile might be corrupted.
PLEASE DO NOT ATTEMPT TO START UP THE INSTANCE
without following the steps below.
RE-STARTING THE INSTANCE CAN CAUSE SERIOUS DAMAGE
TO THE DATABASE, if the controlfile is truly corrupted.
In order to re-start the instance safely,
please do the following:
(1) Save all copies of the controlfile for later
analysis and contact your OS vendor and Oracle support.
(2) Mount the instance and issue:
ALTER DATABASE BACKUP CONTROLFILE TO TRACE;
(3) Unmount the instance.
(4) Use the script in the trace file to
RE-CREATE THE CONTROLFILE and open the database.
Please let me know, how i need to proceed. Major problem is i am not able to put the db in mount state. I have both spfile and pfile.
Thanks in advance.

user13162661 wrote:
Thanks Pavan for yoour response, but how can i find, which is good copy of the controlfile?
Now i have 3 controlfiles in spfile or in pfile, Can i directly remove the 1 and 2 controlfiles from pfile and put the 3rd there itself and start the db.
startup pfile='file_path';
Is there any thing i am missing?
Please helpout.
control file '/u02/oradata/beacondp/control02.ctl' version 390158 inconsistent with file '/u01/oradata/beacondp/control01.ctl' version 390097I suspect that control02.ctl is the good one since it has the higher SCN

Pls answer the following questions very urgent.

Hi Experts & Friends,
Can comeone please answer the following questions? If possible try to give some explanation.
1. Why we use ANALYSIS PROCESS DESIGNER??
2. What are web templates?
3. How the connection from SRM SOURCE SYSTEM done?
4. How do u get data frm SQL server thru DB Connect.
5. Process chain, two targets frm same datasource if monthly & daily
6.how u display the scanned & unscanned pdt ?? thru variable replacement type?
Thanks & Regards
Siri

Hi Siri,
1. Analysis Process designer
The Analysis Process Designer (APD) is the application environment for the SAP data mining solution.
The APD workbench provides an intuitive graphical interface that enables you to visualize, transform, and deploy data from your business warehouse. It combines all these different steps into a single data process with which you can easily interact.
Use APD to pre-process your data:
? Read data from different sources and write it to a single location
? Transform data to optimize reporting
? Ensure high data quality by monitoring and maintaining the information stored in your data warehouse.
The APD is able to source data from InfoProviders such as InfoCubes, ODS objects, InfoObjects,
database tables, BW queries, and flat files. Transformations include joins, sorts, transpositions, and with
BW 3.5, integration with BW?s Data Mining Workbench (RSDMWB).
Check here
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/96939c07-0901-0010-bf94-ac8b347dd541
http://help.sap.com/saphelp_nw04/helpdata/en/49/7e960481916448b20134d471d36a6b/frameset.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/39/e45e42ae1fdc54e10000000a155106/frameset.htm
and service.sap.com/bi
https://websmp206.sap-ag.de/~form/sapnet?_SHORTKEY=01100035870000585703&
2. Web Templates
Web Template
Use
This Web item can be used to manage consistent sections of different Web templates centrally within one Web template, which you can then insert into any Web template as required. In this way, you can define a header or footer section with the corporate logo and heading as a Web template and can integrate this Web template into your Web applications as a Web Template Web item. This Web template is then inserted during runtime. In contrast to HTML frame technology, the system does not generate a new page during this process. The context of the main template thus remains the same. In this way, you can display text elements and so on from data providers for the main template in the inserted Web template.
Check....here....
http://help.sap.com/saphelp_nw04/helpdata/en/69/5f8e9346c1244ea64ab580e2eea8b9/frameset.htm
3.Srm Source system Connection
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), ?Automatic recording of changes? and ?Changes to Repository object and cross-client Customizing allowed? 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 ?Logical Systems?: 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 ?RSADMINA Maintenance View?: Details screen:
a.     Choose Display ? Change.
b.     Enter RFCUSER in the BW User ALE field.
c.     Choose Save.
Leave the transaction in order to activate the entries you have made.
2.5     SAP SRM
2.5.1     Define Client Administration
Use
This activity defines changes and transports of the client-dependent and client-independent objects.
Procedure
1.     Access the transaction using:
SAP SRM/ Role Menu     Local Settings ® SAP SRM ® Define Client Administration
Transaction Code     SCC4
2.     Switch to change mode.
3.     Select your client.
4.     Choose details.
5.     Check the entries for currency and client role.
6.     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), Automatic recording of changes and Changes to Repository object and cross-client Customizing allowed is required.
7.     In the Restrictions area, set the flag Allows CATT processes to be started.
This flag must be set. Otherwise, activities using CATT procedures cannot be used for the installation.
Result
Client administration has been defined to support the installation using Best Practices.
2.5.2     Define a Logical System for SAP SRM
Use
The logical system is important for the communication between several systems. This activity is used to define the logical systems for the Enterprise Buyer and back-end system.
Procedure
1.     Access the transaction using:
IMG Menu
Enterprise Buyer      Enterprise Buyer Professional Edition ? Technical Basic Settings ? ALE Settings (Logical System) ? Distribution (ALE) ? Sending and Receiving System ? Logical Systems ? Define Logical System.
Transaction Code     SPRO
2.     For the activity type, select Cross-client.
3.     The following naming convention is recommended:
Log. System     Name
YYYCLNTXXX     Enterprise Buyer System
4.     Save your entries
You have to maintain at least two systems (local Enterprise Buyer system and the SAP R/3 back-end system)
Naming Conventions: XXXCLNT123 (XXX = system ID, 123 = client number)
2.5.3     Assign Logical System to Client
Use
The purpose of this activity is to define the
?     Enterprise Buyer client you will be using
?     Standard currency to be used
?     Recording of changes
?     Capability for your system to use CATT procedures
Procedure
1.     Access the transaction using:
SAP SRM
Role Menu     Local Settings ® SAP SRM ® Assign Logical System to Client
Transaction Code     SCC4
2.     Switch to the Change mode.
3.     Select your Enterprise Buyer client and go to the Client Details screen.
4.     In the Logical system screen, choose the logical system for the client.
5.     Set the currency in the Std currency field to a valid entry, such as USD or EUR.
6.     Make the following settings:
Setting     Values
Changes and transports for client-specific objects     Automatic recording of changes
Restrictions when starting CATT and eCATT     eCATT and CATT allowed
7.     Choose Save.
Using this transaction, you can change from the production client to the development client and back again in the Client role field.
Result
The logical system has been assigned to the client and CATT procedures can be executed now.
2.5.4     Create System Users
Use
This task creates remote users RFCUSER, BBP_JOB, WEBLOGIN   for the SAP R/3 back-end system and for Enterprise Buyer.
Procedure
1.     Access the transaction using:
SAP Menu
Enterprise Buyer      Basis Tools ? Administration ? User Maintenance ? Users
Transaction Code     SU01
2.     Enter RFCUSER in the User field.
3.     On the Address tab Choose Lastname RFCUSER.
4.     Choose Create.
5.     Enter the password LOGIN on the Logon data tab.
6.     As User Type, select System.
7.     Go to the Profiles tab.
8.     Enter the profiles SAP_ALL ,SAP_NEW and S_BI-WX_RFC.
9.     Save your entries.
10.     Repeat this procedure to create the user BBP_JOB (Password: LOGIN).
11.     Repeat this procedure to create the user WEBLOGIN (Password: SAPPHIRE).
Result
The following users have been created.
Client     User     Password
Enterprise Buyer      RFCUSER     LOGIN
Enterprise Buyer     BBP_JOB     LOGIN
Enterprise Buyer     WEBLOGIN     SAPPHIRE
     USER/Password from the Service File of the ITS Installation.
3     Cross Connectivity
This chapter describes all settings that are necessary to connect the components of the SAP.system landscape with each other. The settings for each combination of two components to be connected are described in a separate structure node. The separate section headings make it possible to identify the activities required to connect certain components with each other. The section headings for components that are not part of the installation can be skipped.
3.1     Connecting SAP BW with SAP R/3, SAP CRM, SAP SRM
Procedure
To carry out the activity, choose one of the following navigation options in the SAP BW system:
SAP BW Role Menu     Connecting SAP BW with SAP R/3, SAP CRM, SAP SRM
Transaction code     RSA1
SAP BW Menu     Modeling ? Administrator Workbench: Modeling
1.     Choose Modeling.
2.     Choose Source Systems.
3.     Select Source Systems in the window on the right.
4.     Choose the Context menu (right mouse click).
5.     Choose Create.
6.     Select SAP System from Release 3.0E (Automatic Creation).
7.     Choose Transfer.
8.     Make the following entries:
Field     Entry
Target computer (server)                            Server of the SAP R/3, SAP CRM or Sap SRM system
System ID     System ID of the SAP R/3, SAP CRM or SAP SRM system
System number     System number of the SAP R/3, SAP CRM or SAP SRM system
Background user in source system     RFCUSER
Password for source system     LOGIN
Background user in BW     RFCUSER (can not be changed in this activity)
Password for BW user     LOGIN
9.     On the dialog box Please log on as an administrator in the following screen choose Continue.
10.     Log on to the Source System with your administrator user. Choose the correct client.
11.     On the dialog box New Source System Connection choose Continue.
12.     On the Replicate Metadata dialog box, choose Only Activate.
4.data frm SQL server thru DB Connect
Check here....
http://help.sap.com/saphelp_nw04/helpdata/en/a6/4ee0a1cd71cc45a5d0a561feeaa360/content.htm

ML81N Enhancement to trigger the 'Release Strategy'..very urgent !!

Similar Messages

Maybe you are looking for