Organisational structure replication through ALE

Hi Gurus,
Can you guide me how to do organisational structure replications through ALE.
The transaction to be used are BD21 .
I have tried and i am not able to see any IDOCS in green colour without error.
Can anybody explain me the process in detail.
Kind Regards,
Shruti

Hi Shruti,
Pease check this in Org,Replication /Org.Model
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/f03e6f6c-8c16-2a10-1581-ed8812e2effe&overridelayout=true
and take help from ur ABAP'r also.
Thanks
Swati

Similar Messages

HR Organisation Structure replication to SRM

What are the limitations of replicating the HR Organisation Structure to SRM.
I believe its always better to create a new one in SRM.
Pls advise.
Thanks,
Venky

Hi,
See this thread:
HR WITH SRM
BR,
Deepti.

Organisational Structure replications

Hi,
Does anyone have a best practice guide or something as to the best methods for managing oranisational replications from ECC to SRM. Over the years I have encountered many of the same issues such as users becoming detached and muliple business partner creation when changed IDOC are posting.
I was just wondering anyone else had looked at this in detail?
Kind regards

Hi Andrew,
Can you please make sure the following note & all related notes have being applied in your system:
550055 = EBP/CRM: New integration for business partner
1168104
These needs to be in place to help stop inconsistencies.
Kind Regards,
Edel.

Organisational structure replication

Hi,
We have 2 structures HR and SRM structure.We are making HR structure as main structure and want to replicate to SRM.
Both structures are different HR structure has the FI table where the approvers are sitting for bujet appoval.SRM structure there is logistics from where the workflow gets approved by different approvers.Now my question is this we want both structures to be similar as we are going to do testing .Datasheets will also be based on this .We need a clean part of org structures which will be same in org and srm .How should i extract data from both systems and what objects and relationships i must extract.How can i upload the data. I know your answer will be BDC but then how to do that is my question
Kind Regards,
Shruti

Hi Shruti,
You want to replicate ur HR structure to SRM and both should be same now main points
--> Identify all the main objects(Org.Units,Sub units,Positions and their relationships)
-->Cost Center and their relationship with the Org.unit/positions.
-->Create a new plan version as 10 - Test Plan Version
Now use RE_RHCOPY00 put plan version as 01 and copy from the exsting one to another created i.e. 10 so now u copy the exesting one to a new one in just a new plan version.
Download this to an Excel and plzz ensure what changes u want.
Let me know once ur done with this.
Thanks
Swati

Issues in employee replication from ECC to CRM through ALE/IDOC

Hi,
We are replicating the employees from ECC to CRM through ALE/IDOC.
Some times for some employees, the Idoc status in CRM is 52(Application document not fully posted) in CRM (WE02 tcode)
If I see the details its showing as " Identification Category BPCCOD is Not Assigned to Any Identification Type"
What I need to do now to avoid this.
Pl suggest
Regards
BABU.

Hi Babu, I'm having the same error when I replicate my employes. I have define BPCCOD in spro - Cross-Application Components - SAP Business Partner - Business Partner - Basic Settings - Identification Numbers, but this configuration does not resolve my problem.
Could you resolve this problem?.
Pls. let me know...
Regards,
George

Organisation Structure is not replicating completely from R/3 to CRM

Hi SAP Gurus,
Plaese help me out in this issue.
We are replicating organisation structure from R/3 to CRM. There is Org Structure in which there are some sub org units say 6, under main org unit with positions and jobs. When try to replicating by tcode PFAL with evaluation path OS-CP, it geneartes IDOC in R/3, all are succesfully processed and Green. IN CRM, these Idocs are red and yellow with staus 51 and 52. As a result of this partial, org structure is replicated to CRM. In CRM, the Idoc is failed and It shows following errors:-->
1. Resource key 4AFBD7B949F406E9E10000000B7404B7 is not known (Status 51)
2. HR: ALE inbound processing for HR master data (Status 52)
3. No Filter, No Conversion, No Field converted.
Plaese advice to resolve this issue.
Thanks a lot,
Kind Regards
Ash
Edited by: Raman Khatri on Nov 23, 2009 2:43 PM
Edited by: Raman Khatri on Nov 23, 2009 2:47 PM

You can copy exactly error ??..
For replication you need use tx PIDE in R3.
In folder CRM>R3 you assign "BP Classification: Consumer, Customer, Sales prospect, competitor" to account group in R3. The BP Classification is hard code in CRM and only are available 5 types of classification.
In folder R3> CRM you assing Account group R3 to CRM Classifcation and grouping. Grouping CRM is done in SPRO > Cross-Application Components >SAP Business Partner > Basic Settings > Number Ranges and Groupings > Define Groupings and Assign Number Ranges.
Then, you define filter for replication in tx R3AC1 and replicate with tx R3AS

Determining Approver from Organisational Structure

Hi all,
I am new to Workflow, Can anyone please let me know how Approver can be determined from Organisational Structure.
1) For determining Approvers i have position data available with me.
2) Also please let me know all possible scenarios of determining the Approvers from Organisational Structure.
Please provide me any Documents or tutorials available for the same, if possible.

There are many ways to determine the agents.
Rule : It can be used via Function module(by abap coding & need to be suffixed with US for User & respectively) or Responsibilities created at Rule level or directly using Organization and there are many other options provided at that level.
Organization: To assign the whole Organization and it is mostly high level & workitem will be sent to all the users assigned to that Organization.
Position: To assign the Position directly assigned & workitem will be sent to all the users holding that position.
Coming about your question:
1) For determining Approvers i have position data available with me.
You can either assign it at User Decision level directly or if you want to do any validations, you can even do it in Custom method or Function module through RH_GET_STRUCTURE where you need to pass Position & retrieve Users.
You can look at the below link:
http://help.sap.com/saphelp_nw04s/helpdata/en/fb/135d7c457311d189440000e829fbbd/frameset.htm
Questions are welcome.

SRM 5.0 organisational structure

Hi Gurus,
is there a restriction for the number of persons integrated in the SRM (SRM 5.0) org. structure (PPOMA_BBP)? Is there a sizing guideline? We plan to expand the number of buyers and approvers up to 90.000.
Many thanks in advance,
Dirk

Hi
Welcome to world of SRM !!!
Please go through the following links, which will definitely help ->
Re: Org Model Report
Re: I want to replicate organisation structure tree of pposa screen?
Re: USERS_GEN and the 200 Limitation
If an organizational structure with a large number of dependent nodes is displayed in the overview area, access to the transaction can take a very long time.
This type of large organizational structure can occur when the vendors are transferred from the back-end system.
Please refer to the following SAP OSS Notes ->
Note 503915 - PPOMA_BBP: performance improvement overview area
Note 389869 - Organizational unit with many employees
Note 405806 - Transaction PPOMA_BBP for new material group attributes
Note 864221 - EBP 4.0+: Performance location
Note 920158 - EBP 4.0+: Shopping cart performance
Note 1044096 - RSWUWFMLEC: Wrong Emails and/or Bad Performance
Also please see this SAP Consulting Note ->
Note 1095895 - Slow response times for several SRM transactions
Re: SRM Org Structure - Vendor Root
Hope this will definitely help. Do let me know, Hope this will answer all your queries.
Regards
- Atul

Define sd organisational structure?

define sd organisational structure?

SD Configuration:
Enterprise Structure:
1. Maintaining Sales Organization
Sales Organization is an organizational unit responsible for the sale of certain products or services.
IMG -> Enterprise Structure -> Definition -> Sales and Distribution -> Define, copy, delete, check Sales organization
2. Assigning Sales Organization to Company Code
This assignment ensures all the sales made through this Sales Organization are accounted for in the assigned Company Code (Company Code is created by FI Consultant).
IMG -> Enterprise Structure -> Assignment -> Sales and Distribution -> Assign Sales Organziation to Company Code
3. Maintaining Distribution Channel
Distribution Channel is the way, in which Products or Services reach Customers.
IMG -> Enterprise Structure -> Definition -> Sales and Distribution -> Define, copy, delete, check distribution channel
4. Assigning Distribution Channel to Sales Organization
This assignment ensures, a Sales Organization can supply Materials to Customers through this Distribution Channel.
IMG -> Enterprise Structure -> Assignment -> Sales and Distribution > Assign distribution channel to sales organization
5. Maintaining Division
Division is a way of grouping materials, products, or services.
IMG -> Enterprise Structure -> Definition -> Logistics - General -> Define, copy, delete, check division
6. Assigning Division to Sales Organization
IMG -> Enterprise Structure -> Assignment -> Sales and Distribution -> Assign division to sales organization
7. Setting up Sales Area
All the sales are made from a particular sales Area. For creating a Sales Order Sales Area is compulsory.
IMG ->Enterprise Structure -> Assignment -> Sales and Distribution -> Set up sales area
8. Assigning Sales Organization- Distribution Channel- Plant
Plant is created ny MM Consultant.
IMG -> Enterprise Structure -> Assignment -> Sales and Distribution -> Assign sales organization - distribution channel - plant
9. Define Shipping Points
Shipping Point is the Organizational element, which is responsible for shipping the Materials to the Customers.
IMG -> Enterprise Structure -> Definition -> Logistics Execution -> Define, copy, delete, check shipping point
10 Assigning Shipping Point to Plant
This assignment ensures that goods from different Plant can be dispatched from different Shipping Points.
IMG -> Enterprise Structure -> Assignment -> Logistics Execution -> Assign shipping point to plant
Note: Ensure to do the undermentioned configuration also though it is not in Customizing node of Enterprise Structure.
11. Defining Common Distribution Channels for Master Data
Use
The purpose of this activity is to define distribution channels which have common master data..
Procedure
Access the activity using one of the following navigation options:
IMG Menu -> Sales and Distribution -> Master Data -> Define Common Distribution Channels
Transaction Code: VOR1
12. Defining Common Divisions for Master DataUse
The purpose of this activity is to define distribution channels which have common master data..
Procedure
Access the activity using one of the following navigation options:
IMG Menu -> Sales and Distribution -> Master Data -> Define Common Division
Transaction Code: VOR2
Pricing Procedure
In SD, Pricing Procedure is determined based on Sales Area (Sales Organization + Distribution Centre + Division) + Customer Pricing Procedure + Document Pricing Procedure. Sales Area is determined in Sales Order Header Level. Customer Pricing Procedure is determined from Customer Master. Document Pricing Procedure is determined from Sales Document Type / Billing Type (if configured). Once the pricing procedure is determined, Condition records are fetched. If appropriate condition records are found, the price is determined. If Mandatory pricing condition is missing, system will through an error message.
In SD, the steps to configure Pricing procedure are as under:
Step 1:
Condition table: If existing condition table meets the requirement, we need not create a new condition table. Considering the requirement for new condition table, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Condition Table (select the required fields combination, which will store condition record).
Step 2:
Access Sequence: If existing access sequence meets the requirement, we need not create a new access sequence. Considering the requirement for new sequence, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Access Sequence (Access sequence is made up of Accesses (Tables) & the order of priority in which it is to be accessed. Here we assign the condition table to access sequence.
Step 3:
Condition Type: If existing condition type meets the requirement, we need not create a new condition type. Considering the requirement for new condition type, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Condition Type. It is always recommended to copy an existing similar condition type & make the neccessary changes. Here we assign Access sequence to Condition type.
Step 4:
a. Pricing Procedure: It is recommended to copy a similar pricing procedure & make the neccesary changes in new pricing procedure. Pricing Procedure is a set of condition type & arranged in the sequence in which it has to perform the calculation. Considering the requirement for new Pricing Procedure, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Pricing Procedure --> Maintain Pricing Procedure.
b. Pricing Procedure: After maintaining the pricing procedure the next step will be determination of pricing procedure. Configuration for determining pricing procedure in SPRO is as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Pricing Procedure --> Determine Pricing Procedure.
5. Condition record: Condition record is a master data, which is required to be maintained by Core team / person responsible from the client. During new implementation, the condition records can be uploaded using tools like SCAT, LSMW, etc.
Normal Sales Order Cycle:-
Step 1: Sales Document Type
IMG > Sales and Distribution > Sales > Sales Documents >
Sales Document Header:
1. Sales Document Type:The sales document types represent the different business transactions, such as Inquiry, Quotation, Sales Order, etc. To create new sales order type, always copy as with reference to similar sales order. If possible use standard sales order.
2. Define Number Ranges For Sales Documents: Maintain number range with discussion with core team.
3. Assign Sales Area To Sales Document Types:
A. Combine sales organizations / Combine distribution channels / Combine divisions: Ensure to maintain these, else Sales Order creation will give error.
B. Assign sales order types permitted for sales areas: Assign only required Sales Order Types to required Sales Area. This will minimize selection of Sales Order Type as per sales area.
Sales Document Item:
1. Define Item Categories: If possible use Standard Item Category. Incase if required to create new, copy as from standard & maintain New.
2. Assign Item Categories: If possible, use standard. Formula for deriving item category: Sales Document Type + Item Category Group + Usage + Higher Level Item Category = Item Category
Schedule Line:
1. Define Schedule Line Categories: If possible use Standard Schedule Lines. Incase if required to create new, copy as from standard & maintain New.
2. Assign Schedule Line Categories: If possible, use standard. Formula for deriving Schedule Line: Item Category + MRP Type / No MRP Type.
Step 2:
IMG > Logistic Execution > Shipping > Deliveries >
1. Define Delivery Types: If possible use Standard Delivery Type. Incase if required to create new, copy as from standard & maintain New.
2. Define Item Categories for Deliveries: If possible use Standard Item Categories for Delivery Type. Incase if required to create new, copy as from standard & maintain New.
3. Define Number Ranges for Deliveries: Ensure to maintain number range.
Step 3:
IMG > Sales and Distribution > Billing >
1. Define Billing Types: If possible use Standard Billing Type. Incase if required to create new, copy as from standard & maintain New.
2. Define Number Range For Billing Documents: Ensure to maintain number range.
3. Maintain Copying Control For Billing Documents: Maintain relevant copy controls such as Sales Order to Billing, Deliver to Billing, etc.
The configuration differs from scenario to scenario & requirement of the client.
Regards,
Rajesh Banka
Reward point if useful.

Organisational structure --- Mapping

Hello dear Experts ...... This is venkat charan a new commer to SAP SD .
My question is..... how to MAP organisation structure in REAL TIME? What r the steps involved in this ? please help me ?

Hi Venkat Chanran,
Please find the details below.
Client:
Client is an environment where we are working. A client is an organisation term it is an independent unit in the system, each unit consist of own environment and there fore its has own master data or transaction data assigned ,user master records and chart of accounts.
Master data:
The data, which is the basis for all the SD processing.
Type of Master Data:
1.Organizational data: this is the structure of the company where by each business is represented by a hierarchical element.
2. Customer master data: the data where all data regarding customer and material are stored.
3. Documents: the business transaction is stored in the documents.
4. Global Settings: it is one in which we define country keys and currencies.
Company code:
Legal entity and an independent accounting unit at company code level, where we create balance sheet and profit and loss accounts.
Sales organization:
An organizational unit that sells and distributes products, negotiates terms of sale, and is responsible for these transactions.
Distribution channel:
Channel through which materials or services reach customers. Typical distribution channels include wholesale, retail and direct sales. You can assign a distribution channel to one or more sales organizations.
Division:
Product groups can be defined for a wide-ranging spectrum of products. For every division you can make customer-specific agreements on, for example, partial deliveries, pricing and terms of payment. Within a division you can carry out statistical analyses or set up separate marketing.
Sales area:
Combination of Sales organisation, Distribution Channel, and division.
Sales Office.
Geographical aspects of the organization in business development and sales are defined using the term sales office. A sales office can be considered as a subsidiary.
Sales offices are assigned to sales areas. If you enter a sales order for a sales office within a certain sales area, the sales office must be assigned to that area.
Sales Group.
The staff of a sales office may be subdivided into sales groups. For example, sales groups can be defined for individual divisions.
Salespersons.
Individual personnel master records are used to manage data about salespersons. You can assign a sales person to a sales group in the personnel master record.
Plant:
A plant is a place where either material are produced or goods and services provided.
Storage location:
Where we store the material.
Shipping point:
It is a physical location where we load the goods in order to deliver.
Loading point:
It is a point where we load and unload the material by means of equipments.
Business Area.
A unit in an enterprise, grouping product and market combinations as homogeneously as possible for the purpose of developing unified business policy.
Financial Accounting (FI).
A business area is an organizational unit within financial accounting which represents a separate area of operations or responsibilities within an organization.
The system posts costs and revenue according to the business area.
The business area can be Assigned to the:
sales area (if the accounts are to be posted according to sales)
plant/division (if the accounts are to be posted according to products)
Financial accounting transactions can be allocated to a specific business area.
Credit control area.
Organizational unit in an organization that specifies and checks credit limits for customers. A credit control area can include one or more company codes. It is not possible to assign a company code to more than one credit control areas.
ENTERPRISE STRUCTURE
STEP 1: DEFINE COMPANY
MENU PATH: IMG u2013 ENTERPRICE STRUCTURE
FINANCIAL ACCOUNTING u2013 DEFINATION u2013 DEFINE COMPANY T.C: SPRO
Select the line 1000 and go for details and then click copy, enter the company details and save it. (ctrl s)
step 2: edit copy check delete company code
select the line 1000 go for details and then say copy , fill the details of company code. Then a address screen appears and fill the details .
then save it.
Now go for the next option
We will fine the below screen and click copy button
Press enter
Say yes
Say yes
for the remaining screen say yes to all , now the system will copy the table to your company code.
After copying below screen u will see and the say transport
In below screen u enter u r company code.
the above screen u will see is the transport request screen
Step 2: logistic general
We will get the below screen enter the details of the plant and also fill the address details of the plants and save it
then save it
DEFINE DIVISION:
HERE GO FOR NEW ENTRIES DIRECTLY BECAUSE NO DETAILS ICON IS THEIR.
SALES AND DISTRIBUTION
ENTER ALL THE DETAILS AND SAVE
2. DISTRIBUTION CHANNEL
GO FOR MENU PATH . DEFINE DISTRIBUTION CHANNEL
THEN SAVE IT
DEFINE SALES OFFICE:
MATERIAL MANAGEMENT
THIS IS NOT OUR CONFIGURATION; THIS IS THE PART OF MM CONSULTANT.
DEFINE STORAGE LOCATION
LOGISTIC EXECUTION:
DEFINE SHIPPING POINT
HERE ALSO THE SAME PROCEDURE ,
Select the line 1000 go for details and say copy. Enter the details of shipping point and save it.
The above are the definition part, now we have to link the organizational elements. The linking can be configured with the help of menu path: Img - enterprise structure - assignment
Note: what we have defined in respective module, the same we have to assign with respect to the module.
ASSIGNMENTS:
1. FINANICIAL ACCOUNTING:
ASSIGN COMPANY CODE TO COMPANY:
THEN SAVE IT.
LOGISTIC GENERAL
1. ASSIGN PLANT TO COMPANY CODE:
GO FOR THE COMPANY CODE AND HIGHLIGHT IT, NOW CLICK ASSIGN THEN SELECT THE PLANT IN THE POP UP SCEEN AND PRESS OK, WE HAVE TO GET THE BELOW SCREEN
NOTE : BUSINESS AREA CONCEPT IS VERY IMPORTANT.
SALES AND DISTRIBUTION ASSIGNMENTS
1. ASSIGN SALES ORGANISATION TO COMPANY CODE T.Code : OVX2
2. ASSIGN DISTRIBUTION CHANNEL TO SALES ORGANISATION
T.CODE: OVXK
3. ASSIGN DIVISION TO SALES ORGANISATION
T.CODE: OVXA
4. SET UP SALES AREA:
T.CODE : OVXG
5. ASSIGN SALES OFFICE TO SALES AREA
6.ASSIGN SALES ORGANISATION u2013 DISTRIBUTION CHANNEL u2013 PLANT
T.CODE : OVX6
NO MATERIAL MANAGEMENT ASSIGNMENT OF STORAGE LOCATION
WHY BECAUSE WE HAVE ALREADY MAINTAINED IN THE PLANT, SO IT IS AN ASSIGNMENT.
LOGISTIC EXECUTION
ASSIGN SHIPPING POINT TO PLANT:
NOW OUR ENTERPRISE STRUCTURE IS READY
Result :
Go for Img u2013 enterprise structure u2013 definition u2013 define company u2013 edit copy check delete company code u2013 structure u2013 navigation u2013 double click your created company code. T. code: EC01
Please Reward If Really Helpful,
Thanks and Regards,
Sateesh.Kandula

Transfer of inforecord condition types through ALE

Hi,
I want to know how to transfer Inforecord Condition Types other than PB00 through ALE.For condition type PB00,we can use msg type COND_A & t-code MEK3.Similarly, what are the corresponding values for other condition types like FRA1 etc.
Thanks,
Kaveri

Hi,
If we are loading the conditions by IDoc type COND_A, we do not give the transaction code, instead we specify the table (like KVEWE = 'A' & KOTABNR = '025' for the Inforecords with plant level conditions), We give the condition records to structure E1KONP with condition PB00 as first condition followed by other conditions ( example RA00, RA01) in sequence as per the condition schema mentioned.
So you can load the FRA1 condition the same way, just feed the LSMW the condition record FRA1after PB00.
Hope this helps.
Best Regards, Murugesh

Can we move the Organisation structure from DEV to Quality to Production?

Hi Experts,
Can we move the Organisation structure from DEV to Quality to Production?
If yes, I believe that we have to change backend details at some areas.
Please any one provide procedure and precautions for doing this, In general how we have to proceed?
Thanks
Reshma

Hello Reshma,
See program documentation from PFAL transaction (ALE distribution of HR Master Data).
You will need:
- an evaluation path,
- a distribution models for sender DEV > receiver QUAL and sender QUAL > receiver PROD for correct message type.
Regards.
Laurent.

Report for Purchase Orders didnt reach target through ALE

Hi Experts,
we are sending Purchase Orders to Third party system using XI.
But some of the orders when we save its automatically system generating output medium is PRINT so these orders not going through ALE.
1)Can anyone please tell me why the system is generating PRINT instead of ALE distribution.
2) is there any report for how many purchase orders created for the day and how many of them gone through successfull using ALE distribution.
Answer will be rewarded.
Kiran

Hi
Have you configured the PO Output type/messages with the Medium as 'A'(ALE)
otherwise the system willd efualt take 1(print) as default medium.
Check the NAST table entries for that date created Output type of PO's
for all of them the Medium(NACHA) field should be A
then all will go through ALE
check them.
Regards
Anji

Is it possible to create all views in MM01 through ALE(MATMAS) ?

Hi,
I want to create all views(One or two may not require) in Inbound MATMAS through ALE. Is it possible ?
Currently its creating only Basic data1 & 2,General Plant Data/Storage1 &2 ,plant stock.
I didn't set any filter for any segments.
Please don't post ALE or EDI document. I already have enough documents.
Thanks,
Narayan

I solved by myself. Set PSTAT to whatever view you want.
Thanks,
Narayan

Is it possible to create all views in Material master through ALE(MATMAS) ?

Hi,
I want to create all views(One or two may not require) in Inbound MATMAS through ALE. Is it possible ?
Currently its creating only Basic data1 & 2,General Plant Data/Storage1 &2 ,plant stock.
I didn't set any filter for any segments.
Please don't post ALE or EDI document. I already have enough documents.
Thanks,
Narayan

I solved by myself. Set PSTAT to whatever view you want.
Thanks,
Narayan

Organisational structure replication through ALE

Similar Messages

Maybe you are looking for