Allocation Structure - Maintenance in production system

Hi all,
is there any way of maintaining the allocation structures (KSES) in production without opening the system (modifying the client status)?
Thanks in advance for your replyes!!!

Hello Sadishivan,
The idea is not to create the allocation structure in production directly, but to be able to maintain the assessment cost element or even insert a new assigment, without the need of a Transport Order.
As example, the maintanance of Cycles is not modificable by default, but there is an option to maintain them in a not modificable mandt by implementing note OSS 326080.
I didnt find any OSS Note which would allow to do that with the allocation structures... but maybe there is another way of maintaining them in a not modificable mandant?
Thanks again for the reply

Similar Messages

Allocation structure maintenance

Hi Experts
How do i add a cost element in the cost element group to include it as a source in OKO6?
one of the users was trying to settle internal orders but got an error " KD503 - Complete allocation structure Z1" the error went on to say cost element 480010 needs to be included in the Z1 allocation structure.
only problem is that when i go into the structure under Source, there is a cost element group already maintained with 4 other cost elements, i want to add this cost element (480010) into the group.
please help
Thanks

Hi Srikanth,
i have tried adding the cost element into the desire group, and it didnt give me any errors. i asked the user to try and settle the order and it was successful. thank you so much.
if i may ask, what impact is this change going to have the system, because the user says he just want to enter it settle it then remove it again from that group.
initially i had suggested that he should reverse the posting, but he said it would be a long process because the payment has been done and they got discounts for it.
what effect do you think this will have on the system or in reporting?

Update Purchasing group directly in production system

Hi,
We keep getting purchasing group changes requests and we follow conventional approach, configure in development - move to Quality and then to Production.
Since we have high number of requests, we are exploring the direct maintenance in Production system. Please advise on the best approach to this.
thanks
Mahesh

there is an alternative missing.
you can change a customizing activity to be a master data activity, and you do not need to have the PRODuction system open for customizing..
this is explained in OSS Note 135028 - Transfer IMG activity to current setting
However, I have made my experience in the past as I joined my current employer. In this system the purchasing groups were maintained in production system, which I did not know, and some key user did not know too, as they asked me to add a new purchasing group. I did this in the development system and transported to prouction.
And it happened, that I added a purchasing group in developement that was already accopied in production, so the entry in production got overwritten with my transport. so for a couple of days 2 buyers worked with the same purchasing group, they did not even realize it, as nobody is really looking at a PO form if a system is live for many years. This caused some trouble with statistics and as well with communications between vendors and us.
a second experience was made by the fact that people had deleted purchasing groups, after buyers had left the company. But SAP validates the existing of purchasing groups when archiving purchase orders. So I had to recreate all deleted purchasing groups before I could continue with archving.
I think that this experience is reason enough to not give this customizing activity into user hands.

While Doing Production Order Settlement "Complete Allocation structure" :

Dear Experts
I am Getting This Problem ,
please give me A suitable Solution.
I am created Another Allocation Structure And Assigned to Settllement Profile . But it is not trigering. Not Capturing That allocation
Complete allocation structure Z1
Message no. KD503
Diagnosis
During settlement, the system puts the sender debits into groups (assignments), which are settled using the same settlement cost element. The settlement assignment is made in the allocation structure, which is stored in the settlement rule for the sender (under settlement parameters).
Cost element 40512006 cannot be assigned to a settlement cost assignment in allocation structure Z1, and therefore it cannot be assigned to a settlement cost element.
Procedure
Possible solutions are as follows:
u2022 If the posting under cost element 40512006 was made to the sender because of an incorrect entry, and you can reverse the posting, and do not need to update the allocation structure. You only need to reverse the incorrectly assigned posting before repeating the settlement. Exception: For an investment measure with a line item settlement, you need to extend the allocation structure, even after the reversal.
Edited by: rajamallu on Jul 2, 2010 10:41 AM

Hi,
within allocation structure customizing you create assignments for allocation structure Z1.
Each assignment has a source (cost element, cost element range, cost element group).
The cost element 40512006 is not included in the source definition of allocation structure Z1 but there are values to be settled available on your sender.
Thus they cannot be settled and thats why the message occurs. So maintain alloc. structure Z1 completely.
Best regards, Christian

Index value maintenance directly in a Production system

Hi,
Is it possible to control the access to T-code: REAJINDX ( Index value maintenance) by Authorization Management (Profile Generator/Role management) in a closed system (Production) for configuration?
Authorization Object: S_TABU_NAM
Activity: 02
Table: V_REAJINDXCLASS
The requirement is the Index value maintenance directly in a Production system (closed system for the configuration) through the Authorizacion Management.
Thanks and best regards,
Fernando

Hi Franz,
First, thanks for your quick response. I haven´t got to solve the problem with these notes. I would like to explain in further detail the issue and the current system configuration.
The configuration for the Client (T000) is the following:
Client Role: T (Test) or P (Production)
Changes and Transport for Client-Specific objects: No Changes Allowed
Cross-Client Objects changes: 3-No Changes to Repository and Cross-Client Customizing objects
The configuration for the object VC_REAJINDX (SOBJ) is the following:
Category: CUST
Transport: 2-Automatic Transport
Adjustment: Automatically adjustable
Current Settings: Marked
With this configuration at client level and for this object, it is not possible to maintain the Index values in the target client. Then my question (doubt) is if it´s possible to maintain the index values in despite of this configuration by Authorization management (User roles/Profile Generator) for this object (Example: Give authorization to modify this object (in order to maintain the values) to a Key User with a specific role, SU01). Or if it´s not possible, then It´s necessary to change the configuration for the object (VC_REAJINDX) for the fields, Category, or/and Transport,... For this option, it´s necessary to modify the SAP standard using a Developer key and I´m not sure if it is a recommended solution.
But my client wants to maintain the index values directly from PRD system and not from a DEV system and after transport the updates to PRD.
On the other hand, the error message that the system shows it isn´t the message number TK430, It is the message nº SV052, No maintenance authorization for requested data (Diagnosis: You have attempted, in change mode, to access data for which you have no authorization.). This is the reason I think, maybe, it is possible to control it through the Authorization management.
Thanks in advance and best regards,
Fernando

Message no. KD503 - Complete allocation structure K1 for Internal Order

Hi,
During Internal order settlement through KO88 I am getting this error as :
Message no. KD503 - Complete allocation structure K1
Diagnosis :
During settlement, the system puts the sender debits into groups (assignments), which are settled using the same settlement cost element. The settlement assignment is made in the allocation structure, which is stored in the settlement rule for the sender (under settlement parameters). Cost element 430500 cannot be assigned to a settlement cost assignment in allocation structure K1, and therefore it cannot be assigned to a settlement cost element.
Procedure :
    Possible solutions are as follows:
    o   If the posting under cost element 430500 was made to the sender because of an incorrect entry, and you can reverse the posting, and do not need to update the allocation structure. You only need to reverse the incorrectly assigned posting before repeating the settlement. Exception: For an investment measure with a line item settlement, you need to extend the allocation structure, even after the reversal.
    o   If the posting was made correctly, you can do the following:
a) You can assign a different allocation structure to the sender: In the master data maintenance for the sender, choose
    "Settlement rule -> Goto -> Settlement parameters" and then enter a different allocation structure. If necessary, also check whether the correct allocation structure is entered in the settlement profile. The allocation structure is defaulted in the settlement profile when you create sender master data or when you maintain the settlement rule.
-   You can update allocation structure K1
The same configuration in Development Server there is no error but problem occurs in Quality server. Here the process is Internal Order creation - Creation of Reservation through MB21- Goods Issue against reservation through MB1A and finally settlement through KO88. During settlement this error occur. In configuration setting of allocation structure under Internal Order I have mentioned only revenue settlement (as per business) against assignments. Under source mentioned cost element group and under settlement cost elment Receiver Cat is "CTR" and tick "By Cost Element".
During MB1A i.e, goods issue accounting entry is generated as
81(Dr). 430500 Constimptuion Saprae and Stores
99(Cr). 310411 Inventory Machinery and Spare.
During settlement this debit figure should credit. But not allowiing to credit. Even in configuration under settlement cost element if I remove the tick of "By cost element" and mention secondary gl account whose cost element category is 21, still showing the same error in QA server. What may be the probabale solution ? Even if i remove allocation structure K1 from settlement profile 20 still same error exist. How this link gets during settlment inspite of removing allocation structure from settlement profile...
NB.. COPA is not implemented in our company. So PA structure should not arrise here....
Thanks & regards,
Samrat
Edited by: Samrat Roy on Aug 30, 2010 7:28 PM

Hi Samrat,
The issue is very simple.. Cost element 430500 is posted in your IO...
While settling you have 2 options... Either you can credit the original GL account 430500.. This happens when you tick "By Cost element".. This you have done already...
2nd option is not to tick "By Cost element" and assign a secondary cost ele category 21...
But for any of these options to work, you have to include GL 430500 in the "source"... The above 2 options apply only to those GL accounts which are mentioned in the "Source".... for rest of the GL accounts, system gives this error
Include 430500 in your "source" cost ele group.. Error will be resolved
Regards
Ajay M

Error : complete allocation structure while doing Ko88 settlement.

Message no. KD503
Diagnosis
During settlement, the system puts the sender debits into groups (assignments), which are settled using the same settlement cost element. The settlement assignment is made in the allocation structure, which is stored in the settlement rule for the sender (under settlement parameters).
Cost element S10100 cannot be assigned to a settlement cost assignment in allocation structure A2, and therefore it cannot be assigned to a settlement cost element.
Procedure
Possible solutions are as follows:
If the posting under cost element S10100 was made to the sender because of an incorrect entry, and you can reverse the posting, and do not need to update the allocation structure. You only need to reverse the incorrectly assigned posting before repeating the settlement. Exception: For an investment measure with a line item settlement, you need to extend the allocation structure, even after the reversal.
If the posting was made correctly, you can do the following:
a) You can assign a different allocation structure to the sender: In the master data maintenance for the sender, choose "Settlement rule -> Goto -> Settlement parameters" and then enter a different allocation structure.
If necessary, also check whether the correct allocation structure is entered in the settlement profile. The allocation structure is defaulted in the settlement profile when you create sender master data or when you maintain the settlement rule.
You can update allocation structure A2

Dear,
Please refer my reply in this thread,
Error in Rework order settlement
Regards,
R.Brahmankar

Delete COPA value fields in a productive system

Does anyone have practical experience with deleting COPA value fields in a productive system?
The issue is that old, no longer used value fields should be deleted from a productive system to allow creating new ones, as the maximun number of value fields is reached.
An alternative would be to delete the prior transaction data captured on these no longer to be used value fields and rename them for their new use (to avoid that different kind of old and new data is reported on the same value field).
I am refering to the documentation on transaction KEA0 (or OSS note 160892 up to release 4.5), where it is mentioned that deleting value fields should only be done for operating concerns that have not yet been used productively. Did anyone do this already in a productive system?
Cheers, Peter

To delete characteristics or value fields, you should perform the following
activities:
1. Delete the corresponding characteristics and value fields from
Customizing in all clients (this includes forms, reports, planning
layouts, and so forth). To locate characteristics and value fields, use
the appropriate where-used list in the Customizing Monitor. You can
access it by choosing Tools -> Analysis -> Check Customizing Settings
(TA KECM).
You can jump directly from the where-used list to the relevant
Customizing transaction and then delete the appropriate field there.
2. Switch to the screen for maintaining the data structure of an
operating concern (Maintain operating concern).
3. If you need to effect other changes to the datastucture for the
operating concern before making any deletions, effect those changes and
save the data structure.
4. In order to be able to select the fields of the data structure,
choose Extras -> Characteristics (or Value fields) -> Unlock.
5. Select the characteristics and value fields to be deleted and remove
them from the data structure with the "Reset fields" function.
6. Reactivate the operating concern. The system starts by checking
whether the operating concern contains any data and whether the fields
to be deleted are still being used in any Customizing settings.
7. If none of the fields are still in use, the system then starts the
re-activation. If the operating concern does not contain any data or
does not require the database system to be converted, the tables are
activated. You are then able to activate the environment for the
operating concern. In this case, the following activities no longer
apply.
If the operating concern already contains data, a system message tells
you that the database needs to be converted. If you proceed, an
activation log appears (at the top of the list).
8. Analyze the activation log. If it only contains error messages
telling you to convert the tables, proceed with the next activity.
You must otherwise remove the cause of the errors before the tables can
be converted. In this case, you should answer "No" to the next prompt,
which asks whether the conversion transaction should start.
9. If you still only receive error messages telling you to convert the
tables, choose "Back" and start the conversion.
10. Plan a job for the conversion. A list of the tables to be converted
is shown for this. If the tables only contain a small amount of data
(less than 10 000 records), then all the tables can be converted in one
job. In that case, you can select all the tables.
For larger tables, conversion should take place in several jobs.
However, you should ensure that table CE4xxxx (where xxxx = operating
concern) is the last table to be converted.
Warning. No other changes can be made to the operating concern during
the conversion.
A copy of the table is generated during the conversion. The database
system should have sufficient memory available for this copy.
To schedule conversion as a job, use the "Schedule selections" function.
You can display the current status of the conversion by selecting the
"Refresh" icon. Tables disappear from the list once they have been
converted sucessfully. If a conversion is taking a while, it is also
possible to leave the transaction. You can then continue the conversion
using DB requests -> Mass processing in one of the following ways:
With the job overview. You access this by choosing System -> Services ->
Jobs.
Using the database utility transaction. You access this by choosing
Utilities -> Database Utility in the ABAP Dictionary menu.
You can use the status function to call up the status of the operating
concern during operating concern maintenance. You need to activate all
tables after conversion.
11. To analyze errors that have occurred during the conversion, you can
use the database utility transaction by choosing Extras -> Logs. The log
has the same name as the conversion job: TBATG-date. You can also
restart the conversion with this transaction.
For more information on the database utility, choose Help -> Application
help while still in the above transaction.
12. Once you have activated all the tables in the operating concern,
generate the operating concern environment from within operating concern
maintenance.
You can then use the operating concern again.
Please, refer to the IMG documentation under Controlling ->
Profitability Analysis -> Structures -> Define operating concern
-> Maintain operating concern, for further details.
Hope it helps

Allocation Structure

Hi,
When we execute the T.code KO88(Order Settlement for AUC), showing the below Error Message.
Complete allocation structure A1
Message no. KD503
Diagnosis
During settlement, the system puts the sender debits into groups (assignments), which are settled using the same settlement cost element. The settlement assignment is made in the allocation structure, which is stored in the settlement rule for the sender (under settlement parameters).
Cost element 410006 cannot be assigned to a settlement cost assignment in allocation structure A1, and therefore it cannot be assigned to a settlement cost element.
Procedure
Possible solutions are as follows:
If the posting under cost element 410006 was made to the sender because of an incorrect entry, and you can reverse the posting, and do not need to update the allocation structure. You only need to reverse the incorrectly assigned posting before repeating the settlement. Exception: For an investment measure with a line item settlement, you need to extend the allocation structure, even after the reversal.
If the posting was made correctly, you can do the following:
a) You can assign a different allocation structure to the sender: In the master data maintenance for the sender, choose "Settlement rule -> Goto -> Settlement parameters" and then enter a different allocation structure.
If necessary, also check whether the correct allocation structure is entered in the settlement profile. The allocation structure is defaulted in the settlement profile when you create sender master data or when you maintain the settlement rule.
You can update allocation structure A1
We have assigned Cost element for Receiver Cat. FXA.
What is the Problem?
Thanks in advance

In the allocation structure you need to include the source CE 410006.
Allocation Structure>Assignments (double click)>Source (double click)
Here in source you should have the CE mention in From else you should have created a CE group including this CE.
And now for this source ensure you've maintained the Settlement cost element (for FXA) either 'By Cost Element' or Settlement cost element.
Regards
Sreenivas

Error In allocation Structure when doing settlement to GL from WBS

Hi All,
I got this error message. What should i do? I try to check my allocation structure...but it seem correct.
Complete allocation structure Z3
Message no. KD503
Diagnosis
During settlement, the system puts the sender debits into groups (assignments), which are settled using the same settlement cost element. The settlement assignment is made in the allocation structure, which is stored in the settlement rule for the sender (under settlement parameters).
Cost element 901000 cannot be assigned to a settlement cost assignment in allocation structure Z3, and therefore it cannot be assigned to a settlement cost element.
Procedure
Possible solutions are as follows:
If the posting under cost element 901000 was made to the sender because of an incorrect entry, and you can reverse the posting, and do not need to update the allocation structure. You only need to reverse the incorrectly assigned posting before repeating the settlement. Exception: For an investment measure with a line item settlement, you need to extend the allocation structure, even after the reversal.
If the posting was made correctly, you can do the following:
a) You can assign a different allocation structure to the sender: In the master data maintenance for the sender, choose "Settlement rule -> Goto -> Settlement parameters" and then enter a different allocation structure.
If necessary, also check whether the correct allocation structure is entered in the settlement profile. The allocation structure is defaulted in the settlement profile when you create sender master data or when you maintain the settlement rule.
You can update allocation structure Z3

Hi Sreenivas ,
The accounting document looks weird :
Hi,
Settlement profile : ZPS001
GL, CC, Order, WBSE and FXA optional
Document type : SA (GL Account doc)
Distribution rule : 10
Residence time : 24
Allocation strucutre Z3
Default object type : FXA
tick on % settlement and equivalence no
to be settled in full
Allocation structure : Z3
Assignment : 1.Labour ,2.MAterial, 3. Subcontract
Source : 1. PSlabour , 2.PSmaterial 3. PSsubcon 4.Cost
Settlement cost center : FXA (ticl by CE), CTR (settlement cost element 90200) ; ORD (Settlement cost element 902001); GL put 747100f
I already successfully settle from WBS to GL 747100(settlement receiver) However, when i check FB03 it shows that
GL account 747100
Posting key 40
Amount 25000
GL Account 747100
Posting key 50
Amount -25000
What the problem ?
Cheers,
Nies

Complete allocation structure Z4 Message no. KD503

Complete allocation structure Z4
Message no. KD503
Diagnosis
During settlement, the system puts the sender debits into groups (assignments), which are settled using the same settlement cost element. The settlement assignment is made in the allocation structure, which is stored in the settlement rule for the sender (under settlement parameters).
Cost element 90001000 cannot be assigned to a settlement cost assignment in allocation structure Z4, and therefore it cannot be assigned to a settlement cost element.
Procedure
Possible solutions are as follows:
If the posting under cost element 90001000 was made to the sender because of an incorrect entry, and you can reverse the posting, and do not need to update the allocation structure. You only need to reverse the incorrectly assigned posting before repeating the settlement. Exception: For an investment measure with a line item settlement, you need to extend the allocation structure, even after the reversal.
If the posting was made correctly, you can do the following:
a) You can assign a different allocation structure to the sender: In the master data maintenance for the sender, choose "Settlement rule -> Goto -> Settlement parameters" and then enter a different allocation structure.
If necessary, also check whether the correct allocation structure is entered in the settlement profile. The allocation structure is defaulted in the settlement profile when you create sender master data or when you maintain the settlement rule.
You can update allocation structure Z4
Please help resolve error below.
What do I need to reverse?
Is there a different way to enter actual cost for this?
What do you think is missing in my allocation structure?

Hi paul
This error message you are getting KD503
This message comes up at the time of settlement of the order when you are transferring the cost from on cost object to the other. Here you are giving the final cost settlement on the asset so the final asset is where all the cost is going to get settle for the cost which you have taken in the internal order. you have to define a roadmap for the cost elements which is carrying the cost from the IO to the final asset.
The resolution Is do the following: go to KO88 and explore the juke box where you have booked all the jv take note of all those cost elements now come to KSES and here under Z4 allocation structure give CO area and go to source tab and give the range of cost elements that you have used in ko88 and save it
This will resolve your issue.
Kind regards
Arman
SAP FICO

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.

Transaction LS10 - mass creation of WM storage bins - in Production system

Hi,
Does someone know, if it is possible to make the Transaction LS10 open in a production environment where the customizing is
blocked for changes.
In the reality the users need to have this Transaction for Creating new bins in massive way. Up to now it is job of the IT and then
release the change request to production. But also the generation of the new bins is only in production system possible, when
it is open for a short term to create the new bins.
thanks for you help in advance
Michael

Thanks for your question. I know LS05.
I (and the users) want especially use LS10 and create also in Production mew sequences and structures.
do you know a possibility for this?
thanks

Problem during import of 121 transport requests to productive system

Hello
We have problem during import of transport requests to productive system. Import of 121 transport requests stopped very soon in phase "N" (in TRBAT I have only one entry and in TRJOB as well).
In sm50 there is an BGD running under user DDIC in client 000 now for 14453 seconds (program SAPLSDB2). This should be import.
In SM37 I can see it as job "RDDGEN0L" with repport"RDDGENBB". Based on some literature it should perform "Converting all structure changes generated by the import and recorded in table TBATG, other than the structure changes to matchcode objects." Very interesting that TBATG has only four entries related to 2 indexes in table "DFKKOPK" , one in table "DFKKREP06" and one" ENQU" for EFKKEXC". (only this last one has not status error)
For fist two indexes I know they are not present as objects "LIMU""INDX" in any transport request beeing imported.
Also on productive system there is no"VOL" and "ZOL"indexes for table "DFKKOPK"(instead they are created on test system ie. not transported from development to test system)
Last command for that process is "CREATE INDEX "DFKKOPK~HKO" ON "DFKKOPK" ("MANDT", "HKONT", "OPBEL") PCTFREE 10 INITRANS 002 TABLESPACE PSA
PTR3 STORAGE (INITIAL 0000000016 K NEXT 0000000016 K MINEXTENTS 0000000001 MAXEXTENTS UNLIMITED PCTINCREAS"
There is enaught space on disk and in tablespaces (it is an oracle/HPux server).
Does anyone knows workaroun to solve production

are you importing these transport requests simultaneously into production?
I would suggest you try doing in smaller groups of 5 or 10 and then see whether you are able to import the requests
Rohit

Short dump "EXSORT_NOT_Enough_MEMORY" in production system

Hi,
"EXSORT_NOT_Enough_MEMORY" dump occuring in production system,Could any one please tell me how to fix this dump.
Please refer the error message below
What happened?
    The current ABAP program had to be terminated because the
    ABAP processor detected an internal system error.
    The current ABAP program "RSBPCOLL" had to be terminated because the ABAP
    processor discovered an invalid system state.
Error analysis:
    The current ABAP/4 program was meant to sort a dataset (internal table
    or extract). For reasons of capacity, this was not possible due to
    insufficient main storage space. Therefore, the
    external sort was called and resulted in the following error:
    the following error:
    SAP runtime system internal error.
               Last error logged in SAP kernel
    Component............ "EM"
    Place................ "SAP-Server cambsvr15_PEC_00 on host cambsvr15 (wp 12)"
    Version.............. 37
    Error code........... 7
    Error text........... "Warning: EM-Memory exhausted: Workprocess gets PRIV "
    Description.......... " "
    System call.......... " "
    Module............... "emxx.c"
    Line................. 1886
and i see that background job "SAP_COLLECTOR_FOR_JOBSTATISTIC" job being failed with below error.
Job started
Step 001 started (program RSBPCOLL, variant , user ID BACKGROUND)
ABAP/4 processor: EXSORT_NOT_ENOUGH_MEMORY
Job cancelled
Please help me to correct this error.
Best Regards,
Vinod

Hi Bhaskar,
yes, I have checked the Wp status and it looks fine.I'm getting this error on My PRD system on regular basis since 1 week.
We have tried to restart the server but no luck.
Here are the ST02 values and background job SAP_COLLECTOR_FOR_JOBSTATISTIC also being failed with this error.
Buffer              Hitratio    Allocated       Free space          Dir. size      Free directory        Swaps
                          [%]         [kB]           [kB]      [%]      Entries       Entries    [%]
Program                   99.11       400,000        1,481     0.38      100,000      90,774    90.77       36,307
CUA                       99.31         3,000          264    10.53        1,500       1,263    84.20       14,934
Screen                    98.45         4,297           27     0.82       10,000       9,653    96.53         645
Calendar                  99.76           488          359    75.10          200          48    24.00         0
OTR                      100.00         4,096        3,439   100.00        2,000       2,000   100.00         0
SAP memory              Current use      Max. use In memory   On disk
                        [%]      [kB]       [kB]       [kB]       [kB]
Roll area              1.45      3,808     7,680    262,144         0
Paging area            3.40      8,904     13,056       0        262,144
Extended Memory        9.05    389,120    812,032 4,299,776
Swaps
        0
   21,249
        0
   16,399
   36,307
   14,934
      645
        0
        0
      272
        0
210,742
        0
Please let me know if you require further information.
Thanks & Regards,
Vinod

Allocation Structure - Maintenance in production system

Similar Messages

Maybe you are looking for