Partner Determination/Organization Structure

Hi,
I wanted to understand how through partner determination procedure relevant Service Team can be assigned. You can use example of Standard Service Order Transaction SRVO, Standard Partner Determination Procedure 00006, Standard Access Sequence 011 Executing Service Organization, Standard Organization determination rule 1000278 and organization structure 50004983 to explain the connection.
Thanks
Deepak

Hi Deepak,
The description of rule 10000278 says,"
This rule should be used for partner determination via the orgdata model.
It delivers on the basis of orgattribute <H>executing
service organizations</>
It is intended
- for partner determination at item level
- for service items
- when using products in the service item
Executing service organizations are all
in the orgdata model with the following characteristics:
- Service Scenario
- Indicator for executing service organization is set.
These partners are filed as partners of the partner function
category executing service organization in the
transaction.
For example, org data determination is set up in the container after
the postal code and product.
regards,
Prashant
<b>"please REWARD the points "</b> if it helps..!!

Similar Messages

  • Determination of KM document approvers from ECC Organizational Structure

    Hi,
    As part of a requirement of my client, I need to determine the approvers of the KM folders automatically from the HR organizational structure that resides in the ECC side.
    e.g. I want the document approval process to be started by the approval of my Finance specialist, then go on with the approval of Finance manager he/she is reporting to in the organizational structure and last with the approval of Finance director.
    The organizational structure is as follows:
    HR Director
    |
    HR Manager
    |
    HR Specialist
    The scenario mentioned above cannot be solved with roles or groups because the reporting relationship between the specialist and manager is of importance for the approval process.
    Please suggest a way to determine approvers from the HR Organizational Structure on the ECC side. This does not have to be a standard solution and can involve some extra coding.
    Thanks in advance for your support.
    Best regards,
    Dilek

    Hi SK,
    I think it will be a total gross injustice to the robustness that the SAP GTS offers while executing global trade if you opt for asynchronous check for sales order and this is a very rare business case.
    If anyhow a check is required for which the SAP GTS system is being used and if it is executed in real time rather than without any delay, then I see no reason to implement your suggestions as such.
    But you can opt for asynchronous check by deactivating the functional module which is called when a sales order is saved and which transfers the latest recorded changes to the SAP GTS system.
    For your second requirement, I can say if the GTS system has not checked your sales order, then how it can but a block on it instantaneously when the GTS system is up. For this you either need to wait for a while or get some customized code in play for placing a block automatically when a sales order is saved.
    Regards,
    Aman

  • Partner Determination in PO and OBDLV

    Hey @ all,
    what I am trying to do right now is to implement a simple, customer specific partner determination procedure. For that I want to add a partner role and partner to an purchase order on header level.
    The only place I found where I could add this partner is in BAPI_PO_CREATE1. But this BAPI is not used when I create a PO with the GUI (ME21N).
    So do you have an idea, where I could add a an additional partner to the PO (User-Exit, Badi, Enhancement Spot ...)?
    The same thing I want to do with the outbound delivery (VL01N). There is User-Exit MV50AFZ1 available. But there is the question: How do I add a partner within this user exit (structures to edit...).
    Thanks for you help in advance,
    Rolf
    Edited by: Rolf Kasel on Mar 10, 2010 1:57 PM

    Hi,
       If its specific to plant and vendor, then check whether the plant specific partner function has been activated.
       Go to MK02 - partner function and go to menu - extras - Add. purchasing data and check whether "Data retent. at plant level allowed" flag is marked as shown below.
       If so, go to menu - extras - Alternative data.
    Click on partner details:
    Here, system will show plant specific partners.
       Here, maintain the partner function PI for the plant and check the scenario again.
    Another option would be to maintain the higher level search flag in the partner function configuration as highlighted below:
       Now, system will search partners at purchase organization level, if no partner function is found at plant level.
    Regards,
    AKPT

  • SD Organizational Structure

    Hi All
    Could you please send me material you have regarding SD certification?
    I will reward points.
    Many Thanks.
    Message was edited by:
            Ramesh Kollepara
    Message was edited by:
            Surya

    dear surya
    ENTERPRISE STRUCTURE
    Company Code: - It is the company for which we implement SAP.
    NOTE: - It is defined by FI Consultants.
    Sales Organisation: - It is the organizational unit, which is responsible for the sales activities in the company.
    Distribution Channel: - It is the channel through which goods are reaching the customers.
    Divisions: - The range of products or services that the company manufacturing falls into different divisions.
    Sales Area: - It is the combination of sales Organisation, distribution channel and Division.
    Sales Line: - It is the combination of Sales Organisation and distribution channel.
    Sales Office: - It is the Geographical aspect of the structure.
    Sales Group: - The employees in a sales office can be divided into different sales groups.
    Plant: - The factory is called the plant in SAP.
    RELATIONSHIPS:
    Company code to Sales Organisation: - One company code can have many sales organizations. But one Organisation has to be assigned to one company code. So the relation is one to many.
    Sales Organisation to Distribution channel: - One Organisation can have many distribution channels. One Distribution channel can be assigned to many organizations, so the relation is Many to Many.
    Sales Organisation to Division: - One Organisation can have many divisions. One division can be assigned to many organizations. So the relationship is Many to Many.
    Distribution channel to Division: - One Distribution channel can have many divisions. One division can be assigned to many Distribution channels. So the relationship is Many to Many.
    NOTE: - Division is always Organisation specific.
    NOTE: - If sales Organisation wants to use a plant that plant must be
    assigned to the Sales Organisation.
    Logistics
    Sales and Distribution
    Basic Function and Master Data in Sales and Distribution
    Master data in Sales and Distribution
    Organisational Structures
    Organisational Structures in Sales and Distribution
    Defining Sales Organisation: -
    SPRO
    Enterprise Structure
    Definition
    Sales and Distribution
    Define Copy, Delete, Check Sales organization [EC04]
    Go to Define Copy, Delete, Check Sales organization,
    Go to Copy Organisational Object,
    Come back
    Define Sales Organisation
    Select defined sales Organisation and go to details.
    Select the Address icon & maintain the details and save it.
    NOTE: - To unlock the locked data use the Transaction code SM12.
    Rebate Process Active: - It controls whether rebate processing is active for a particular sales Organisation.
    Defining Distribution Channel: -
    SPRO
    Enterprise Structure
    Definition
    Sales and Distribution
    Define Copy, Delete, Check Distribution Channel [EC05]
    Go to Define Copy, Delete, Check Distribution Channel
    Go to Copy Organisational Object,
    Come back
    Go to Define Distribution Channel
    Select defined sales Organisation and give the required name and save it.
    Defining Division: -
    SPRO
    Enterprise Structure
    Definition
    Sales and Distribution
    Define Copy, Delete, Check Division [EC06]
    Go to Define Copy, Delete, Check Division
    Go to Copy Organisational Object,
    Come back
    Go to Define Division
    Select defined division and give the required name and save it.
    Defining Sales Office: -
    SPRO
    Enterprise Structure
    Definition
    Sales and Distribution
    Maintain Sales Office
    Go to New entries and define the sales office
    Go to Address Icon and maintain the details and save it.
    Defining Sales Group: -
    SPRO
    Enterprise Structure
    Definition
    Sales and Distribution
    Maintain Sales Group
    Go to New entries and define the Sales Group
    Go to Address Icon and maintain the details and save it.
    Defining a Plant: -
    SPRO
    Enterprise Structure
    Definition
    Logistics General
    Define, Copy, Delete, Check Plant [EC02]
    Go to copy organisational object
    Come back
    Go to Define Plant
    Select the defined Plant and go to details Address and Maintain Details and Edit details and save it.
    Defining Company Code: -
    SPRO
    Enterprise Structure
    Definition
    Financial Accounting
    Edit Copy, Delete, Check Company code [EC01]
    Go to Define Company and save it.
    Assigning Sales Organisation to the Company Code: -
    SPRO
    Enterprise Structure
    Assignment
    Sales and Distribution
    Assign Sales Organisation to Company Code [OVX3]
    Select the Company Code and go to assign from the list of sales Organisations and select required Sales Organisations and assign and save it.
    Assigning Distribution Channels to Sales Organisations: -
    SPRO
    Enterprise Structure
    Assignment
    Sales and Distribution
    Assign Distribution Channels to Sales Organisation [OVXK]
    Select the Sales Organisation and go to assign from the list of the Distribution Channels and select required Distribution Channels and assign and save it.
    Assigning Division to Sales Organisations: -
    SPRO
    Enterprise Structure
    Assignment
    Sales and Distribution
    Assign Division to Sales Organisation [OVXA]
    Select the Sales Organisation and go to assign from the list of the Divisions and select required Divisions and assign and save it.
    Defining Sales area: -
    SPRO
    Enterprise Structure
    Assignment
    Sales and Distribution
    Setup Sales area [OVXG]
    Select the Sales Organisation and assign Distribution channels
    Select the distribution channel and assign the divisions and save it.
    Assigning Sales Office to Sales area: -
    SPRO
    Enterprise Structure
    Assignment
    Sales and Distribution
    Assign Sales Office to Sales are [OVXM]
    Select the required Sales Area and assign the Sales Office.
    Assigning the Plant to the Company Code: -
    SPRO
    Enterprise Structure
    Assignment
    Logistics General
    Assign Plant to Company code [OX18]
    Select the Company code and assign the required Plants.
    Assigning the Plant to Sales Organisation: -
    SPRO
    Enterprise Structure
    Assignment
    Sales and Distribution
    Assign Sales Organisation – Distribution Channel – Plant [OVX6]
    Select the required sales line and assign the required Plants.
    2. MASTER DATA (MD)
    Master Data is divided into:
    Customer Master Data&#61672;
    Material Master Data&#61672;
    Conditions&#61672; Master Data
    Customer Material Information Record&#61672;
    1. Customer Master Data: -
    Logistics
    Sales and Distribution
    Master Data
    Business Partner
    Customer
    Create
    XD01 – Complete
    Change
    XD02 – Change
    Display
    XD03 – Display
    The Customer Master Data contains 3 screens:
    a. General Data
    b. Company Code Data
    c. Sales Area Data
    Each screen contains different tab pages; each tab page contains different fields.
    a. General Data screen: -
    Marketing Tab Page: -
    Customer Classification: - Specifies a classification of the customer for
    Ex: - classifies the customer as a bulk buyer or it can be based on turnover.
    Defining Customer Classification: -
    SPRO
    Sales and Distribution
    Master data
    Business Partner
    Customers
    Marketing
    Define Customer Classifications
    Go to new entries and define and save it.
    Unloading Points Tab page: -
    Unloading Point: - Specifies the point at which the material is to be unloaded.
    Goods Receiving Hours: - Specifies the timings in which the customer can receive the goods.
    Defining Goods Receiving Hours: -
    SPRO
    Sales and Distribution
    Business Partner
    Customers
    Shipping
    Define Goods Receiving Hours [OVSC]
    Go to new entries and define and save it.
    Contact persons tab page: - Enter the contact persons of the customer.
    a. Company Code Data Screen: -
    Account Management tab page: -
    Reconciliation Account: - The Reconciliation account in General Ledger accounting is the account, which is, updated parallel to the sub ledger account for normal postings.
    Payment Transactions tab page: -
    Terms of Payment: - Specifies the key for defining payment terms composed of cash discount percentages and payment periods.
    Defining terms of payment: -
    SPRO
    Sales and Distribution
    Master Data
    Business Partners
    Customers
    Billing Documents
    Define terms of payment
    Go to new entries and define and save it.
    Payment History Record: - If we check this field the payment history of the customer will be recorded in his credit management.
    To change the customer details go to xd02 and change the values and save it.
    b. Sales Area Data Screen: -
    Sales Tab Page: -
    Sales District: - Specifies in which district the customer is there.
    Before specifying the sales district we should define the sales district.
    Defining Sales District: -
    SPRO
    Sales and Distribution
    Master Data
    Business Partners
    Customers
    Sales
    Define sales district [OVR0]
    Go to new entries and define and save it.
    Customer Group: - Identifies a particular group of customers (for Ex: -wholesale or Retail) for the purpose of pricing or generating statistics.
    Defining Customer Group: -
    SPRO
    Sales and Distribution
    Master Data
    Business Partners
    Customers
    Sales
    Define customer groups [OVS9]
    Go to new entries and define and save it.
    Customer Pricing Procedure: - This field along with few other fields determines the pricing procedure that is given to a customer. [1]
    Shipping Tab Page: -
    Shipping Conditions: - This field along with few other fields determines the shipping point that is proposed by the system.
    Defining Shipping Conditions: -
    SPRO
    Logistics Execution
    Shipping
    Basic shipping functions
    Shipping point and goods receiving point determination scheduling
    Define shipping conditions
    Go to new entries and define and save it.
    Delivering Plant: - Specifies the plant from which the goods should be delivered to the customer.
    Order Combination: - If we want to combine multiple orders for the customer to create a single delivery we need to check this field.
    Partial delivery per Item: - Specifies whether the customer requires full or partial delivery for the item.
    Maximum partial delivery is 9.
    Billing Documents Tab Page: -
    Rebates: - If the customer wants to receive the rebates check this field.
    If we check this field the customer can get rebates from the company.
    Incoterms: - Incoterms specifies certain internationally recognised procedures that the shipper and the receiving party must follow for the shipping transaction to be successfully completed.
    Account Assignment Group: - This field along with few other fields determines the General Ledger Account to which the sales values are to be posted.
    Tax classification: - Specifies whether the customer is liable for tax or not.
    Partner Functions Tab Page: -
    Sold-to-Party (SP): - The customer who is placing order with the company.
    Ship-to-Party (SH): - The customer who is receiving the goods.
    Bill-to-Party (BP): - The customer on whom the bill is raised.
    Payer (PY): - The customer who pays the bill.
    Creating the Customer: -
    Logistics
    Sales and Distribution
    Master Data
    Business Partner
    Customer
    Create
    XD01
    Change
    XD02
    Display
    XD03
    Enter the Account Group [Here specify whether the customer is a SP, SH, BP or PY]
    Enter the Account Group
    Enter the Company Code
    Enter the Sales Area
    NOTE: - If we get the error sales area is not defined for the customers.
    SPRO
    Sales and Distribution
    Master data
    Define common distribution channels [VOR1]
    And also go to
    Define common divisions [VOR2]
    Defining Account Groups: -
    SPRO
    Financial Accounting
    Accounts Receivable and Accounts payable
    Customer Accounts
    Master Data / Records
    Preparations for creating customer master data / record
    Define account groups with screen layout (customer)
    0001  Sold-to-party&#61672;
    Ship-to-party&#61672;0002
    Bill-to-party&#61672;0003
    &#61672;0004  Payer
    If the definition of the account group we can control the field status. We can make fields mandatory or optional or suppress or display mode.
    Defining the number ranges for Account Groups: -
    SPRO
    Financial Accounting
    Accounts Receivable and Accounts payable
    Customer Accounts
    Master Data / Records
    Preparations for creating customer master data / record
    Create number ranges for customer accounts [XDN1]
    Go to change intervals
    Select the button insert interval and define a number range.
    NOTE: - If we check the field external for a number range it becomes an external assignment. Otherwise it becomes internal assignment.
    Assigning the number ranges for Customer Account Groups: -
    SPRO
    Financial Accounting
    Accounts Receivable and Accounts payable
    Customer Accounts
    Master Data / Records
    Preparations for creating customer master data / record
    Assign number ranges for customer account groups.
    Assign the required number range to the account group.
    Partner determination procedure: -
    SPRO
    Sales and Distribution
    Basic Functions
    Partner determination
    Setup partner determination
    Select setup partner determination for customer master
    Step 1: -
    Defining the Partner Functions: - Here we must not define any partner function.
    Go to partner functions.
    While defining the partner functions if we check the field “Unique” that partner faction has to be unique in the customer master i.e. we cannot have multiple partners of that function in a customer master.
    Step 2: -
    Assigning the partner functions to the Account group: -
    Go to account group’s function assignment.
    Go to new entries and assign the required partner functions to the required account group and save it.
    Step 3: -
    Defining the partner determination procedure: -
    Go to partner determination procedures
    Go to new entries and define and save it
    NOTE: - Procedure contains all the required partner functions.
    Step 4: -
    Placing the required partner functions in the procedure: - select the defined procedure and go to partner functions in procedure.
    Go to new entries and place the partner functions
    If we check the field “Not Modifiable” for a partner function it cannot change in the customer master.
    If we check the field “Mandatory Function” it becomes a mandatory in the customer master and save it.
    Step 5: -
    Assigning the procedure to the Account Group: - Go to partner determination procedure assignment. Assign the procedure to the account group and save it.
    2. Material Master Data: -
    Logistics
    Sales and Distribution
    Master Data
    Products
    Material
    Other Material
    Create
    MM01
    Change
    MM02
    Display
    MM03
    Material master contains different views.
    Enter the material number
    Enter the industry sector
    Enter the material type
    Go to select views
    Select the following views:
    Basic Data 1
    Basic Data 2
    Sales Organisation Data 1
    Sales Organisation Data 2
    Sales General and plant data
    Sales text
    MRP 1
    Accounting 1 and select organisational levels
    Enter the plant
    Enter the sales Organisation then distribution channel
    Basic Data 1: -
    Base unit of measure: - Specifies the unit of measure in which stocks of the material are managed.
    Material Group: - Key that we use to group together several materials or services with the same attributes.
    Defining Material Group: -
    SPRO
    Logistics General
    Material Master
    Setting for key fields
    Define Material groups [OMSF]
    Division: - Specifies in which division the material falls.
    Gross Weight and Net Weight: - Specify the weight of the material.
    Weight Unit: - Specifies the weight unit.
    Sales Organisation Data 1: -
    Base Unit of Measure: -
    Sales Unit: - Here enter the unit of measure in which the material sold. We need to enter a value in this field if the sales unit differs from base unit of measure.
    Note: - If the sales unit differs from the base unit we can maintain the conversion factors. To see that information go to additional data.
    Delivering Plant: - Specifies the plant from which the material is delivered to the customer.
    Cash Discount: - If we check this field we can give cash discounts for this material.
    Tax classification: - Specifies whether the material is liable for tax or not.
    Note: - To leave the tax both the customer and the material must be liable for tax.
    Minimum Order quantity: - Specifies the minimum quantity in the base unit of measure that a customer may order for base material.
    Minimum Delivery quantity: - Specifies the minimum quantity that can be delivered to the customer.
    Rounding Profile: - Key that the system uses to adjust the order proposal quantity to the deliverable units.
    Sales Organisation Data 2: -
    Account assignment Group: - This field along with other fields determines the General Ledger Accounts to which different sales values are to be posted.
    Item Category Group: - It determines the nature of the material we are defining.
    Ex: -
    Standard Item&#61672;NORM
    Service or Delivery&#61672;LEIS
    Third party&#61672;BANS  Item
    BOM Item&#61672;ERLA/LUMF
    Packaging&#61672;VERP
    Sales general / plant: -
    Availability check: - Specifies whether and how the system checks the availability of the material and generating the requirement for the materials planning.
    Batch Management: - Specifies whether the material is managed in Batches.
    Transportation Group: - Grouping of the materials that share the same transportation requirement
    Defining Transportation Group: -
    SPRO
    Logistics Execution
    Shipping
    Basic shipping functions
    Routes
    Route determination
    Define transportation Group
    Loading Group: - Grouping of the materials that share the same loading requirement.
    Defining Loading Group: -
    SPRO
    Logistics Execution
    Shipping
    Basic Shipping Functions
    Shipping point and Goods Receiving point determination scheduling
    Define loading Group
    MRP: - Material Requirement Planning
    MRP 1: -
    MRP Type: - Specifies how the requirement of the material can be planned.
    Accounting 1: -
    Valuation Class: -
    Note: - Before creating the material master we should activate company code for material master.
    Maintain Company codes for Material Management: -
    SPRO
    Logistics General
    Material Master
    Basic settings
    Maintain company codes for material management [OMSY]
    Define Storage Location: -
    SPRO
    Enterprise Structure
    Definition
    Materials Management
    Maintain storage location [OX09]
    Enter the plant number
    Go to New entries
    Extending the Organisational views for the Material Master: -
    MM01-Create.
    Enter the material, which you have already created.
    Copy from material = material
    Select the organisational views
    Select the organisational levels
    In the copy from fields enters the values in which the material has been already created.
    In the fields on the left side of the screen enter the values to which we would like extend the material.
    3. Customer Material Information Record: - We need to maintain this record then the customers are having their own names for the material rather the original names.
    Note: - We need to enter the customer material number in the sales order on
    the “Ordering Party” tab page, when we enter the customer material number in the sales order the system will automatically take the original material number.
    Creating Customer Material Information Record: -
    Logistics
    Sales and Distribution
    Master Data
    Rebate Arrangements
    Customer Material Information
    VD51 – Create.
    Material Number: - In this field enter the original name of the material
    Customer Material: - Here enter the material number by which the customer places order.
    Creating Sales Order: -
    Logistics
    Sales and Distribution
    Sales
    Order
    VA01 – Create
    Enter the order type “OR” & Enter the sales area.
    Note: - To maintain the currency conversion rates use the transaction code
    OC41.
    4. Conditions Master Data: -
    Condition Elements: -
    a. Price
    b. Discount or Surcharge
    c. Tax
    d. Freight
    Ex: - for Condition Types: -
    Price&#61672;PR00 
    Material Discount&#61672;K004
    Customer Discount&#61672;K007
    Customer&#61672;K005  Material Discount
    Freight&#61672;KF00
    Maintaining the values for these condition types is called condition records.
    Maintaining the condition records for condition types is conditions master data.
    Maintaining Condition Records: -
    Logistics
    Sales and Distribution
    Master Data
    Conditions
    Selecting using condition type
    VK11 – create
    Enter the condition type for which you are maintaining conditions Record.
    Select the required key combination
    In the material field enter the material for which we are maintaining the conditions record.
    Enter the amount the system will automatically take currency and the calculation type.
    Valid on and valid to: - The condition record is valid for those orders, which comes from the customer in the specified validity period.
    Scales: - If we want to reduce or increase the amount as the quantity is increase select the condition record and go to scales.
    Note: - Don’t enter any value in the first line.
    Setting upper limit and lower limit: - Select the condition record and go to details.
    Note: - The price information in the sales order can be seen on the conditions tab page.
    3. SALES DOCUMENT PROCESSING (SDP)
    Structure of the Sales Document:
    Header Data: - The general data that is valid for the entire document is recorded in the document header. For Ex: - Sold-to-party, Ship to party, Document date….
    Item Data: - The data in the document header applies to all items in the document but same data applies only two specific items. This data is stored at item level.
    Ex: - Material number, order quantity, ship to party, pricing, plant and
    storage location.
    Scheduling Line Data: - It gives the information about the delivery dates and the corresponding conformed quantities.
    Note: - An item can have multiple schedule lines.
    To see the header data in the sales document. Select the Icon “Display Document Header Details” or select “Go to Header and select any tab page”.
    To see the Item data select “Go to Item and select any tab page” or double click on the item.
    Note: - To Change the Ship to party at the item level select the partner
    tab page and change it.
    To see the schedule line data go to item data and select the tab page schedule lines.
    Creating the Sales Documents with Reference:
    Creating Quotation: -
    Logistics
    Sales and Distribution
    Sales
    Quotation
    VA21 – Create
    Creating Order with reference to Quotation: -
    Logistics
    Sales and Distribution
    Sales
    Order
    VA01 – Create
    Enter the order type “OR” and the sales area.
    Select the button Create with Reference.
    Specify the quotation number and say copy.
    Document Flow: - When we create the documents with reference to some preceding documents it forms a document flow. In this flow if we know one document number with the help of “Document Flow”. We can know the remaining document numbers.
    Note: - To See the remaining document numbers, go to the any sales
    document in the flow and select the icon “Display document flow”.
    Note: - If we get the error the order type is not defined for sales area.
    SPRO
    Sales and Distribution
    Sales
    Sales documents
    Sales documents header
    Assign sales area to sales document types
    Sales Document Types: -
    SPRO
    Sales and Distribution
    Sales
    Sales Document
    Sales Document Header
    Define Sales Document type [VOV8]
    Ex: -
    &#61672;IN  Inquiry
    Quotation&#61672;QT
    Order&#61672;OR
    Returns sales documents&#61672;RE
    &#61672;CS  Cash Sale
    Rush Order&#61672;RO
    Scheduling Agreement&#61672;DS
    Functionality of the sales document type: -
    Sales Document Category: - It’s a classification for the different types of documents that we can process in the sales and distribution system
    Ex: -
    Inquiry&#61672;A
    Quotation&#61672;B
    C  Order&#61672;
    Sales Document Block: - Determines whether the sales document is blocked for use. If we block a sales document type users cannot create new sales documents of this type.
    Number range internal assignment and Number range external assignment: - Number that determines how the documents are to the numbered by the system. It indicates which number range is relevant for document type.
    Creating Number ranges for sales Documents: -
    SPRO
    Sales and Distribution
    Sales
    Sales Documents
    Sales Document header
    Define number ranges for sales documents [VN01]
    Item Number Increment: - Specifies the increment by which you want the item numbers in the sales document to increase when the system automatically generates the item number.
    Sub Item Increment: - This is for sub items.
    Reference Mandatory: - Indicates whether a reference document is mandatory when we create a sales document. If so the indicator also specifies which type of reference document we should use.
    Item Division: - If we check this field the division at the item level is proposed from the material master record of the item otherwise the division we enter in the sales document header also counts for all the items.
    Check Division: - Controls how the system reacts during the sales order processing when the division at the item level differs from the division in the document header.
    Read Info Record: - Determines whether the system read the customer material information record for the sales document type.
    Check Credit Limit: - Specifies whether the system runs credit checks and how it response to the check during the sales order processing.
    Check purchase order number: - Specifies whether the system should check if the purchase order number entered is already existing for other sales document.
    Screen Sequence Group: - Controls which screen we see during a particular transaction and in which sequence they appear.
    Transaction Group: - It’s a grouping that allows you to control certain characteristics of a transaction according to sales document type.
    Document Pricing Procedure: - This field along with few other fields determines the pricing procedure that is proposed by the system.
    Display Range: - Specifies whether the system displays only main items or sub items or all the items in the sales document.
    F code for over view screen: - Determines which overview screen we reach during the sales order processing after we enter the data in the initial sales document screen.
    Quotation Messages: - Set an indicator here if you want to receive a message informing you that open quotations exist when we create a sales document. Depending on the indicator we select the system searches for open quotations in the sales document either at the header level for the customer or item level for the material.
    Outline agreement messages: - This is for agreements.
    Incomplete Messages: - Specifies whether an incomplete document can be saved. If we check this field we cannot save the incomplete document until we enter the missing data.
    Delivery type: - specifies the corresponding delivery document type for the sales document.
    Outbound delivery with reference to&#61672;Ex: - LF  order.
    Delivery Block: - Indicates it the entire sales document is blocked for delivery.
    Shipping Conditions: - If we specify the shipping condition here the value from the customer master record is over return by this value.
    BILLING: -
    Delivery related billing type and order related Billing type: - Specifies the corresponding billing document types.
    Ex: -  Invoice&#61672;F2
    Billing Block: - Indicates whether the item is blocked for billing or not.
    Propose Delivery Date: - If we check this field the system automatically proposes the current date as the delivery date.
    Lead-time in days: - Specifies the number of days after the current date that the sales document uses for the proposal of the requested delivery date.
    Propose P O Date: - If we check this field the system automatically proposes the current date as the purchase order date.
    Contract Data allowed: - This field controls whether we can enter the contract data for the sales document type.
    Item Categories: -
    Inquiry&#61672;AFN
    &#61672;AGN  Quotation Standard Item
    Sales Order&#61672;TAN
    IN&#61672;AFNN
    QT Free&#61672;AGNN  of charge Item
    OR&#61672;TANN 
    Third Party Item&#61672;TAS
    Defining Item Categories: -
    SPRO
    Sales and Distribution
    Sales
    Sales Documents
    Sales Document item
    Define item categories
    Functionality of the Item Categories: -
    Billing Relevance: - Specifies the reference document to create the billing document.
    Pricing: - Specifies whether an item is relevant for pricing or not
    Business item: - If we check this field during the sales order processing the business data that we enter an item is allowed to differ from the business data in the header.
    Schedule Line allowed: - Indicates whether we can create schedule lines for the item.
    Item relevant for delivery: - Indicates whether a text item is relevant for delivery processing.
    Note: - We need to check this field in the item category “TATX”. Which is
    for text items.
    Returns: - If we check this field it becomes a returns item.
    Note: - We need to check this field in the item category “REN”. Which is
    for returns.
    Weight / Volume Relevant: - Indicator that controls whether the system calculates weight and volume for the item in the sales document.
    Credit Active: - Indicates whether the credit management functions are active for the document items.
    Determine Cost: - Indicates whether the system determines the cost of a sales document item during pricing.
    Note: - The cost condition type is “VPRS”.
    Automatic Batch Determination: - If we want to use automatic batch determination for materials handled in the batch active this field.
    Rounding Permitted: - Indicates whether rounding is permitted or not.
    Note: - Depending on the rounding profile specified in the material master the order quantity can be rounded in the sales order.
    Order Quantity = 1: - If we check this field the order quantity for each line item is limited to one.
    Item Category Determination: -
    SPRO
    Sales and Distribution
    Sales
    Sales Documents
    Sales Document Item
    Assign Item Categories
    We have to assign the item category to the combination of
    Sales Document type
    Item category group
    Usage
    Higher lever item category
    Schedule line categories: -
    Defining Schedule line categories: -
    SPRO
    Sales and Distribution
    Sales
    Sales Documents
    Schedule Lines
    Define schedule line categories [VOV6]
    CS  Third party item&#61672;
    Inquiry schedule line&#61672;AT
    Sales order&#61672;CP, CV, CN  schedule lines
    Quotation&#61672;BN
    Functionality of a Schedule Line Category: -
    Movement type: - Specifies the physical or logical movement of materials leading to a change in the stock levels or resulting in the consumption of the material.
    Goods Issue Delivery&#61672;601
    &#61672;602  Returns
    Posting the stock in the plant&#61672;561
    Plant to plant stock&#61672;301  transfer
    Return of the stock transfer&#61672;302
    Item relevant for Delivery: - Indicates whether the item that is related to a schedule line is relevant for delivery or not.
    Order type: - Specifies the order type “NB” purchase requisition.
    Note: - We need to specify, “NB” in this field for the schedule line category “CS” which is used for third party item.
    Requirement/Assembly: - If we check this field the transfer of requirements will take place into the inventory management for a better planning of material requirement.
    Availability: - Specifies whether the system should check the availability of the material.
    Schedule line category determination: -
    SPRO
    Sales and Distribution
    Sales
    Sales Documents
    Schedule Lines
    Assign schedule line categories
    We need to assign the schedule line category to the combination of Item category and MRP Type.
    NORM&#61672;Item category group
    Sales Document
    IN
    AFN
    +MRP Type
    AT Item Relevant Delivery
    QT
    AGN
    +MRP Type
    BN Item Relevant Delivery
    OR
    TAN
    +MRP Type
    CP Item Relevant Delivery
    4. PRICING (PG)
    This concept is based on condition technique.
    It’s the combination of:
    1) Condition Tables
    2) Access Sequence
    3) Condition Types
    4) Pricing Procedure
    1. Condition Tables: - Condition table contain the key fields for maintaining condition records. I.e. in other words condition records are stored in condition table.
    Note: - A condition type can have multiple condition tables.
    Note: - A condition table can be used for multiple condition types.
    Defining condition tables: -
    SPRO
    Sales and Distribution
    Basic functions
    Pricing
    Pricing control
    Define condition tables [V/03]
    Create condition tables
    Enter a table number beyond 600
    From the field catalogue, which is there on the right side of the screen select the required key fields.
    To get the valid on / valid to fields while maintaining the condition records we need to check the field “with validity period”.
    Go to icon Technical View
    The fields which are marked, as footer field appears at the footer level at the condition records and the remaining fields appears at the key level.
    Select the Icon Generate for generating the condition table.
    To save the condition table, select the button Local object.
    2. Access Sequence: - Access sequence is a search strategy with the help of which the system gets the valid condition records. It contains the required condition tables in the required order.
    Note: - If required an access sequence can be used or assigned to multiple
    Condition types.
    Note: - The order in which the condition table are placed in access sequence
    is important generally it is most specific to most generic
    Defining Access Sequence: -
    SPRO
    Sales and distribution
    Basic functions
    Pricing
    Pricing control
    Define access sequences
    Maintain access sequences
    Go to new entries and define the access sequence.
    Select the defined access sequence and go to accesses.
    Go to new entries and place the condition tables in the required order
    While placing the condition tables check the field “exclusive”. By doing so if the system finds a valid condition record in the first condition table it will not go to the next condition table
    Select the condition table and go to fields the system gives the warning message “the field assignment has not yet been made” say enter till we get the fields.
    Repeat the same step for all the condition tables and save it.
    Note: - After defining the access sequence assign it to the corresponding condition type.
    3. Condition Types: -
    Defining condition types: -
    SPRO
    Sales and Distribution
    Basic functions
    Pricing
    Pricing control
    Define condition types.
    Maintain condition types.
    Functionality of a condition type: -
    Access Sequence: - In this field specify the corresponding access sequence for the condition type.
    Condition class: - It is the preliminary structuring of condition types.
    Ex: - Surcharges or discounts and price
    Plus/Minus: - If we specify negative here a condition type becomes discount and if we specify positive it becomes surcharge.
    Calculation type: - Determines how the system calculates price discounts and surcharges in a condition type.
    For Ex: - the system can calculate a price as a fixed amount or as a percentage based on the quantity, weight, or volume.
    Condition Category: - It’s a classification of conditions according to pre-defined categories.
    Rounding Rule: - The rule that determines how the system rounds of condition values during pricing.
    Manual Entries: - Indicator which controls the priority with in a condition type between a condition enter manually and a condition automatically determined by the system.
    Amount / Percent: - If we check this field the amount / percentage of a condition type can be change during the document processing.
    Quantity Relation: - Specifies whether the conversion factors for the units of measure in the condition type can be change during document processing.
    Delete: - If we check this field the condition type can be deleted during the sales document processing.
    Value: - If we check this field the condition value can be changed during the document processing.
    Calculation type: - If we check this field the calculation type can be change during the document processing.
    Item condition: - If we check this field for a condition types it becomes item condition, which has to be enter at the item level only.
    Header condition: - If we check this field for a condition type it becomes header condition, which has to be entered at the header level only
    Ex: - RB00 (Discount).
    Note: - After entering the header condition type click on the button activate.
    Note: - The condition amount of the header condition is copied as it is to all the line items in the document
    Group condition: - If we check a header condition as a group condition the condition amount is distributed proportionately among all the line items in the sales document.
    Valid from & valid to: - specifies the beginning and ending of the validity date that the system automatically proposes when we create condition records for the condition types.
    Scale Basis: - Determines how the system interprets a pricing scale in a condition, for Ex: - the scale can be based on quantity weight and volume.
    Check value: - Indicates whether the sale rates must be entered in ascending or descending order.
    Note: - Header condition won’t be having access sequence.
    4. Pricing Procedure: - Pricing procedure contains all the required condition types in the required order.
    Defining Pricing Procedure: -
    SPRO
    Sales and Distribution
    Basic functions
    Pricing
    Pricing control
    Define and assign pricing procedures.
    Maintain pricing procedures
    Go to new entries and define the pricing procedure.
    Select the defined pricing procedure and go

  • Problems assigning BP to a position in the organizational structure

    I tried to assign a bp to a position in the organizational structure,
    but I receive this message "Object cannot be assigned to object CliC
    Agent in the period 21.12.2006 - 31.12.9999".
    Also, I notice that in the screen, the checkbox where i can select for
    the business partner is missing.
    However, I can assign a user to the org structure.
    Before upgrading, it was working. This is the support packages that it was in.
    SAP_ABAP: Level 9
    SAP_BASIS: Level 9
    PI_BASIS: Level 9
    SAP_AP: Level 6
    BBPCRM: Level 6
    After the upgrade to the following,
    SAP_ABAP: Level 10
    SAP_BASIS: Level 10
    PI_BASIS: Level 10
    SAP_AP: Level 7
    BBPCRM: Level 7
    The assigning of business partner to a position no longer works.

    Hi,
    we're facing exactly the same problem, it was all going well until we went on production.... we applied note 997009 which results in a different error... did you manage to find a solution yet ?
    Regards,
    Jacob.

  • Partner determination rules in sales documents

    Good afternoon Experts
    I'm trying to determine responsible agents in a quotation document by using a rule with responsibilities
    ( in the access sequence of the responsible agent partner function). 
    Could someone please confirm how the rule container gets filled?  
    If the rule is based on a post code my understanding is that the post code of the sold
    to party is passed to the rule container and the responsible agent gets
    determined. Passing the post code to the rule container should be in this case hardcoded.
    What happens though if I need to determine the responsible agent based on another
    piece of information like "sales order type", "client tax classification" .
          -  How does the system know how to fill the rule container?
         -   Do  I need to create a new organizational attribute ? 
    On Sap help I've found :
    "If you use rule resolution using responsibilities, you do not have to assign
    attributes in the organizational model, other than the attributes distribution
    channel and division; these are necessary for showing the sales area."
    Where does the sales area come in for partner determination when using rules with responsabilities ? Is there a mechanism like sold to party/document -> sales area -> organisational attribute => attribute passed to rule container? 
    Any input would be appreciated.
    Best regards
    Razvan Zainea 

    Hi Razvan,
    you can use rules in your partner determination access sequence. Most attributes are filled in document processing for the rule container.
    You mentioned postal code. This is filled from the main partner of the document. The main partner of a sales order is the sold-to party, of an opportunity is the prospect, ....
    If you like a different main partner you can do this via process type customizing (field 'partner function ORG').
    If you need to fill your own container values you can use CRM_ORGMAN_BADI method CRM_ORGMAN_ATTRIB_VALUE_FILL.
    Or as mentioned by Shanto you can use your own logic with COM_PARTNER_BADI.
    Best regards
    Marion

  • Partner determination procedure

    <b>Hi,
    This is for the 1st time i am in this forum.
    Could anyone tell about when the error comes (during creation of sales document-customer master record does not exist), though i have created my own partner determination procedure with new part functions & created cmr successfully too.
    Regards,
    Dash</b>

    Have you created Customer Master Data?
    Steps to create Customer master data:
    <b>2.1.2 Process to Create Customer Master
    2.1.2.1 Initial Screen of Customer Master Maintainance</b>
    Use
    The purpose of this activity is to maintain Customer Master Data. Customer Master Can be created for Sales & Distribution, in which it will be possible to maintain General Data Tab & Sales Area Tab. Alternatively it is also possible to maintain Complete / FI, in which it is possible to maintain General Data, Company Code Data & Sales Area Data (Complete) or General Data & Company Code (F1)
    <b>Procedure</b>
    1. Access the activity using one of the following navigation options:
    SAP Easy Access > Logistics > Sales and Distribution > Master Data > Business Partner > Customer > Create > Sales and Distribution / Complete
    Transaction Code: VD01 / XD01
    Fields to be maintained in Initial Screen (referring Complete):
    Field     Functionality
    Account Group - Take a drop down & select appropriate Account Group (Say, Sold To Party)
    Customer     - Enter manually / Internal by system (Based on Configuration)
    Company Code - Take a drop down
    Sales Organization - Take a drop down
    Distribution Channel - Take a drop down
    Division - Take a drop down
    A Customer can be created with reference to an existing Customer & necessary data can be changed.
    Reference
    Field - Functionality
    Customer     Enter manually
    Company Code - Take a drop down
    Sales Organization -Take a drop down
    Distribution Channel - Take a drop down
    Division - Take a drop down
    <b>2.1.2.2     General Data of Customer Master Maintenance</b>
    Use
    The purpose of this activity is to maintain General Data. General Data is applicable to the customer centrally. Incase of extending Customer to another Sales Area, General data will remain the same.
    <b>Procedure</b>
          Fields to be maintained are as under:
    <u>ADDRESS</u>
    Field - Functionality
    Title     Take a drop down
    Name - Enter manually
    Search Term - Enter Manually (Optional)
    Street - Enter Manually (Optional)
    House No - Enter Manually (Optional)
    Postal Code - Enter manually
    City - Enter manually
    Country - Take a drop down
    Region - Take a drop down
    <u>Control Data</u>
    Field - Functionality
    Vendor - Enter Manually (Optional) – To establish Customer Vendor Relationship.
    Trading Partner - To be maintained incase of Inter-company Customer,
    The above is for Illustration purpose. Please ensure to maintain the fields required.
    <b>2.1.2.3     Company Code Data of Customer Master Maintenance</b>
    Use
    The purpose of this activity is to maintain Company Code Data. This is maintained by an FI person.
    <b>Procedure</b>
          Fields to be maintained are as under:
    <u>Account Management</u>
    Field - Functionality
    Recon. Account - Take a drop down (Mandatory)
    <u>Payment Transaction</u>
    Field - Functionality
    Terms of payment - Take a drop down.
    The above is for Illustration purpose. Please ensure to maintain the fields required.
    <b>2.1.2.4     Sales Area Data of Customer Master Maintenance</b>
    Use
    The purpose of this activity is to maintain Company Code Data. This is maintained by an FI person.
    <b>Procedure</b>
          Fields to be maintained are as under:
    <u>Sales</u>
    Field - Functionality
    Sales Office - Take a drop down
    Currency - Maintain the local / export currency.
    Exch. Rate Type - Maintain ‘M’, incase of export / inter-company(if required) only.
    Cust. Pric. Proc - This is maintained to pick the pricing procedure in Sales Order & Billing Document. It should always be maintained.
    Customer Stat. Gr - This is recommended to be maintained to enable the data to flow to SAP standard report.
    <u>Shipping</u>
    Field - Functionality
    Delivery Priority - Take a drop down & maintain the appropriate for Delivery purpose.
    Order Combination - Maintain the tick
    Shipping Condition - Take a drop down & maintain the appropriate for Delivery purpose.
    Delivery Plant - Take a drop down & maintain the appropriate Plant.
    <u>Billing</u>
    Field - Functionality
    Incoterm - Take a drop down & select. Maintain the Description manually.
    Terms of payments - Take a drop down & select.
    Account assignment Group - Take a drop down & maintain the appropriate. This is very important to be maintained, else it will give an error to release the billing document to accounting.
    Tax - Take a drop down & select ‘0’.
    The above is for Illustration purpose. Please ensure to maintain the fields required.
    Regards,
    Rajesh Banka
    Reward points if Helpful.

  • Business partner of organizational unit is not consistent

    Hi,
    Client is on SRM 4.0. When we are trying to search a user in the org structure, and when clicking on "Check" for this user, it was showing fine. But when we are searching any BP in the org strucutre, then immediately the BP name is vanishing against the BP of the user and when doing the "Check" it is showing the below two messages:
    Business Partner of organizational unit XXXXXXX is not consistent
    User cannot be repaired becasue the organizational unit contains errors
    When checking in BBP_CHECK_USRES, the user is not showing as defective. It is green.
    Similarly, the the organizational unit check is also showing as green.
    System is advising to run BBP_BP_OM_INTEGRATE. When we run this for the org units, these are coming as green.
    Users are able to create the shopping carts and also are able to create confirmations. But the problem is happening for some of the users where the system is not allowing to create shopping basket / confirmation.
    Strange thing is that, when we are searching the user by user id in the org structure, then the check is showing no messages. But if we search the same user using the BP number, then in the check, the messages are coming. And once the messages appear, it is appearing for all the users in the org strucutre even at the root node level.
    Any help is highly appreciated.
    Thanks & Regards,
    Aswini

    Hi Aswini,
    There are some possibilities to raise these kind of errors messages:                                                                               
    1) User with inconsistent data.                                           
    Please, check the instructions described in the following notes:          
    597475 - Repair users with inconsistent address data                      
    -> use the report B_REPAIR_EBP_USER_2 to make the user consistent.        
    419423 - Repairing incorrect EBP users                                    
    350129 - Creating business partner for organizational unit                                                                               
    When you create the Org Units have you fully completed the address        
    data, e.g post coe, telephone/fax number etc..                            
    If not, please enter a full address, save the data and see if this        
    generates the Business Partner.                                           
    Remember, that you can delete this user and create a new user.                                                                               
    2) Error in the positions after HR replication                                                                               
    Please, implement the following notes and retest the scenario:            
    1056873 -  Incorrect SRM users after HR distribution                      
    1016450 - Replication of persons deletes positions in SRM                                                                               
    After implementing these notes you should send the employee               
    corresponsing to the user in error with his position (using               
    transaction PFAL or report RHALEINI in UPDATE mode for all periods.                                                                               
    3) the user was deleted and a new was created and during these two        
    actions the user opened documents. So, in this case, the new user         
    becomes inconsistent                                                                               
    If the user is deleted from SU01 still the BP and S which is related to   
    that user will be retained (we can see this in PPOMA_BBP) transaction.    
    In this case we can create the user again using SU01 and can be attached  
    with the old 'S' and 'BP'.                                                                               
    2. If the user is completed deleted ie., all relations BP and S.          
    The new user has created.   
    In this case if the new user is corrupted we can delete this                  
    user (since the new user doesn't create any documents so far). But the        
    old documents should refer to the new BP related to the new user.   
    ========================
    Also, another option would be to follow the below instructions
    After applying the notes 1056873 & 1016450, send the employees        
    corresponding to the users in errors with their positions (using              
    transaction PFAL or report RHALEINI in UPDATE mode for all periods,           
    using evaluation path A008) ? If not, please do this and it must repair       
    the SRM users. Please test and give me the feedback.     
    Hope this helps,
    Kind Regards,
    Matthew

  • Agent Determination Organizational Data

    Hi Experts,
    Good Day!
    I would like to ask some help regarding a workflow the problem is the "user received the workitem however user claimed that he is not supposed to receive"  that is why i would like to know who are the agents dedicated for these tasks. we are able to find the step it is a user decision where the agent is the Rule "0090010" for purchasing group. In transaction PFAC we entered the rule "0090010" the information regarding the rule below:
    Transaction: PFAC
    Rule Display:
          Basic data:
                   Abbr: Purch. group
                   Name: Purchasing Group
    Rule Definition:
          Category: Agent Determination: Organizational Data
          OrgObj type: T024
    We would like to know:
    1. How does it determine the Agent who is supposed to receive mail using the "Category: Agent Determination: Organizational Data"? Where can we find the agent that is configured on the workflow using the rule?
    2.Is there a standard rule for agent determination: Organizational Data  for this workflow?
    Answer's will be a great help.
    ~Thank You,
    Junne Ray

    got it now! sorry, i am a bit dumb today.
    o.k. here is what you have to check:
    transaction PFOM - relationship between the purchasing group (which will be the one of the PO and therefore and object of table T024) and your organizational structure. check the relationship.
    documentation:
    Data basis for role resolution
    For role resolution, the link between the objects of type
    T024 (individual purchasing groups) and the organization
    objects (position, organizational unit, ...) is evaluated.
    Required settings and Customizing
    The linkages between the various purchasing groups and the relevant
    organizational objects must first be maintained using
    transaction PFOM.
    Procedure for errors
    If the role resolution delivers no result, the work item for which the
    role resolution was carried out is not faulty but addressed to all
    possible processors (flag "abend in role resolution without result"
    is not set).

  • How to determine Organizational Data based on User Login

    Dear all,
    How to determine organizational data based on user login in Activity transaction, currently org determination is happening after entering customer number in the transaction.
    We have used 'Responsibility' determination rule for this configuration. Now the requirement is to determine org data based on user login.
    In Org model we have assigned user to org data through a business partner. But still org data is not getting determined in the transaction.
    Please help me to trace out the problem.. your suggestions will be highly appreciated.
    Best regards
    Raghu ram

    You just have to use other organization determination rule. In your case this would be rule 10000194 (ORGMAN_12). This determination rule delivers the responsible organizational unit of the user
    User is defined as a business partner in the container attribute 'PARTNER'. If not, the system user (sy-uname) is used.
    So you have to do the following:
    - use this determination rule
    - in BP link username with employee
    - assign in PPOMA_CRM employee or user to organizational unit
    This should solve your problem.

  • HOW TO USE ZONE ADRC-REGIOGROUP for Partner determination in opportunity

    Hi Everyone,
    We have an issue link to partner determination.
    We need to determine employee function from the address of the sold-to-party activity person function.
    In fact the REGIOGROUP field within the selected address in the opportunity is what we need to determine the employee function.
    In the meantime we created the attribute REGIOGROUP in the Tcode PPOMA_CRM and we assigned a value to an orgdata.
    We couldn't find any rules or function or Badi that does the link between the regiogroup of the address of the activity person and the attribute with same regiogroup value in orgdata in order to have the employee that works in the regiogroup.
    Do you have any clue about the way to use this regiogroup?
    When we press F1 on the REGIOGROUP field here is documentation we have:
    "Regional structure grouping
    Regional structure grouping combines all elements of the regional structure (cities, streets, street sections). It is used, for example, for clerk determination."
    Does anybody know how to make this clerk determination work? do you know where i could find information about it?
    Many Thanks
    Laurent Monza

    Laurent,
    You can implement the BADI COM_PARNTER_BADI and one of the methods
    DETERMINATION_ADD_IN
    Then you create a new access sequence that uses the exit as the source and assigned that to your partner determination procedure.
    Good luck,
    Stephen

  • Organizational structure creation

    [Organizational Structure creation using HRMD_ABA;
    Appologies if you saw this message on Friday, because I did originally post it under the general area. I was hoping that if I re-posted it under this area I might get a few more responses. I have included the one response I  got, plus my reponse, which does contain more detail about how I ran PFAL - program RHALEINI, and re poses the question about what needs to be created in SRM re an organisational structure, prior to doing an initial load using transaction PFAL.
    Many Thanks
    Claire
    I am trying to set up the organizational structure in our SRM 7.0 system using our ECC 6 organizational structure. I have created all the required distribution models for SRM and ECC 6, and have set up the switch settings in SRM. The number range settings have been set to external.
    As per OSS Note 36317, which concentrates on the initial distribution, and I am working through, I have run PFAL in ECC 6 only for object type O. The HRMD_ABA idocs have been successfully transferred to our SRM system, but all are at status 52.
    The message for all the idoc segments is:
    'You tried to create a relationship from object 01O 50000333 to object 01S 50000846. However, object 01S 50000846 does not exist or is not active in the period from 19000101 to 99991231'.
    One thing I haven't done, which might be incorrect, is create an Organizational Plan in SRM. I specifically haven't done this because I am wanting to use external numbering, and therefore thought the organizational plan would get automatically created as part of the initial distribution.
    Does any one have any idea how to resolve my problem?
    Many Thanks
    Claire
    Re: Organizational Structure creation using HRMD_ABA  
    Posted: Aug 21, 2009 6:03 PM    in response to: Claire Crosby-C...           Reply 
    Hello Claire,
    It looks like you are replicating "S". After the "O" replication you should run the "S".
    Please refer to the OSS note 934372 u201CSRM/CRM: HR integration for business partner u2013 new featuresu201D & SAP Note # 550055 EBP/SRM: New integration for business partner as well.
    Hope this is helpful.
    Thanks
    Ashutosh
    Claire Crosby-C...  
    Posts: 45
    Registered: 3/22/04
    Forum Points: 0 
       Re: Organizational Structure creation using HRMD_ABA  
    Posted: Aug 21, 2009 6:53 PM    in response to: ASHUTOSH TRIPATHI     Edit          Reply 
    Hi Ashutosh
    I intend to replicate 'S', as described in the note, but nothing has been created with my initial replication of 'O'. As per the note 363187 you are supposed to distribute type 'O' first before moving on to 'S'. Is there anything really fundamental I have missed that you are supposed to do in SRM either before or after the initial set of idocs for type 'O' are brought in?
    I have also read the other 2 notes you mention.
    Note 363187 stated:
    'Perform the following steps in the sequence given if the target system is a
    mySAP.com system (SEM, CRM, BBP/EBP):
    1. If you want to use the change pointers for later changes, activate
    them at once. During initial transport, you should not maintain the
    data in parallel in HR because the distribution takes the blocking
    mechanism into account, which can cause an incomplete initial
    transport.
    2. All objects of object type O are distributed with program RHALEINI. As
    a transfer mode, the update mode with infotype 1000 selection should
    be used.
    This way you make sure that all objects of object type O are created
    in the target system for existence checks.
    3. As previous step but for object type C.
    4. As previous step but for object type S.
    So far all I have tried to do is up to step 2.
    When running RHALEINI I have entered the following:
    Objects - Object Type = 'O'
    Reporting Period - Today is selected
    Transfer Mode - Insert is selected, with the Update Mode infotype set to 1000
    I did think making a setting under the Update Mode Infotype seemed a little odd, as I was doing an insert, but is this not what point 2 from the OSS Note is telling me to do?
    Any thoughts would be really helpful.
    Am I supposed to create a skeleton Org structure before pulling in the ECC 6 structure when I am using external numbering?
    Thanks
    Claire

    Hi Ashutosh
    I intend to replicate 'S', as described in the note, but nothing has been created with my initial replication of 'O'. As per the note 363187 you are supposed to distribute type 'O' first before moving on to 'S'. Is there anything really fundamental I have missed that you are supposed to do in SRM either before or after the initial set of idocs for type 'O' are brought in?
    I have also read the other 2 notes you mention.
    Note 363187 stated:
    'Perform the following steps in the sequence given if the target system is a
    mySAP.com system (SEM, CRM, BBP/EBP):
    1. If you want to use the change pointers for later changes, activate
    them at once. During initial transport, you should not maintain the
    data in parallel in HR because the distribution takes the blocking
    mechanism into account, which can cause an incomplete initial
    transport.
    2. All objects of object type O are distributed with program RHALEINI. As
    a transfer mode, the update mode with infotype 1000 selection should
    be used.
    This way you make sure that all objects of object type O are created
    in the target system for existence checks.
    3. As previous step but for object type C.
    4. As previous step but for object type S.
    So far all I have tried to do is up to step 2.
    When running RHALEINI I have entered the following:
    Objects - Object Type = 'O'
    Reporting Period - Today is selected
    Transfer Mode - Insert is selected, with the Update Mode infotype set to 1000
    I did think making a setting under the Update Mode Infotype seemed a little odd, as I was doing an insert, but is this not what point 2 from the OSS Note is telling me to do?
    Any thoughts would be really helpful.
    Am I supposed to create a skeleton Org structure before pulling in the ECC 6 structure when I am using external numbering?
    Thanks
    Claire

  • HEY GUYS!! SMALL QUESTION REGARDING PARTNER DETERMINATION IN AN ACTIVITY

    FRIENDS,
    I WANT THAT I SHUD BE ABLE TO ENTER THE BP NO OF THE ORG UNIT IN A PARTNER FUNCTION AND I AM ABLE TO DETERMINE THE EMPLOYEES RESPONSIBLE. FOR THIS I HAVE FOLLOWED THE PROCESS BELOW. BUT I HAVE BEEN UNABLE TO GET IT. PLZ HELP ME...............
    •Created a partner function “responsible org unit” with function category “ organization responsible” and without relationship category
    •Created one access sequence “responsible org unit &#61664; resp employee” with source “ BP relationships” and assigned the partner function “responsible org unit” in the source of this access sequence.
    •Assigned the partner functions “responsible org unit” and “employee responsible” to the partner det. Procedure.
    •Assigned the access sequence “responsible org unit &#61664; resp employee” to the partner function employee responsible.
    •Maintained blank access sequence for  partner function “responsible org unit” as the “ org unit is not to be determined automatically.
    •In the Master data of the org unit maintained the employees under relationship ‘has employee responsible’.
    NOW WHILE CREATING THE ACTIVITY AFTER GIVING THE BP NO. OF ORG UNIT FOR THE PART. FUNC. “responsible org unit’ THE PARTNER FUNC ‘EMPLOYEE RESP’ SHUD BE DETERMINED BUT ITS NOT HAPPENING.
    I PROMISE THAT POINTS WILL BE GIVEN TO ALL THE HELPFUL ANSWERS
    JAI

    hi pratik,
    let me further clarify my question,
    I dont want to give my org units in the organization tab rather in one of the partner functions. That is why i created one partner function resp. org unit with category organization responsible. Then i have attached the employees under relationship 'employees responsible' to the org units. Then i assign the access sequence with source 'bp relationship' and source partner function 'resp org unit' to the partner function employee resp. in the partner determination procedure.
    IN SHORT I AM TRYING TO GIVE ONE PARTNER FUNCTION MANUALLY AND TRYING TO DETERMINE THE PARTNER FUNCTIONS AUTOMATICALLY USING THE BP RELATIONSHIPS. please give me the way.
    thanks,
    jai.

  • Organization Structure level

    Hi All,
    I know this is a fundamental question, so guide me if this is not the right place.
    I am new to HCM and am trying to get my fundamentals right. I have been reading a lot about organization structure and organization plan. In real life scenarios when we create an organization structure, is it created at a company code level or enterprise (client) level. Bottom line, is there only one organization structure created per client or multiple?
    Thank you!
    Sudhir

    Hi Sudhir,
    Vishru and Vikrant have given you an excellent start.  I believe you are confusing some terms here - Company Code is determined by the Financial organization and refers to a group having their own set of books - general ledger.  There will be at least one Company Code per country but there may be more than one in a country if you have subsidiaries or divisions that keep their own general ledgers. 
    In HR the Organizational Structure shows who reports to whom.  This may cut across several Company Codes as the CEO may manage the heads of several subsidiaries each of which has their own P&L responsibility.  The structure then continues down in each subsidiary again showing who reports to whom.
    The Personnel Area and Personnel Subarea (Enterprise Structure) usually look at location and function - where a person works and their function in the company.  For example, all persons working at the Corporate Headquarters may be in the same Personnel Area if they are all at the same location.  But they may work in Fianance, HR, Purchasing, etc. which may be separate Subareas.  But each Personnel Area may be assigned to only one Company Code.
    The Employee Group and Subgroup (Personnel Structure)determine the type of pay and benefits the employee may receive.  Example, Salaried Employee, Hourly, Union Worker, Part TIme, Full Time, etc.  These will cross Company Code lines if they have the same benefits, work schedules, pay structure, etc. 
    What you must remember is that every employee has an assignment in the Enterprise Structure, Personnel Structure and Organizational Structure and these are all assigned in IT0001-Organizational Assignment. 
    Paul

  • Which access sequence of Partner determination should be used?

    Now my company is upgraded from CRM 2.0c to CRM 5.0 HR1. I found the different result about partner determination on business activity (via transaction code: CIC0) between two version.
    <b>On CRM 2.0C</b>
    <b><u>Tcode: CIC0</u></b>
    Enter sold-to party code: 5300001 as activity partner, Contact person:244 on 'BP searching' workspace. Then on 'Maintain Business Transaction' workspace will display  5300001 as activity partner and 244 as Contact person.
    <b><u>Configuration:</u></b>
    Partner Function: 00000015 Contact person (CRM) using Access sequence 0002
    Access sequence 0002 from activity partner
    Dialog seq:10 has partner origin COM_PARTNER_A Preceding document and mark 'Determine in incorrect source partner'.
    Dialog seq:20 has partner origin CRM_PARTNER_D General business partner model and have origin details; Partner Function category '0006 Activity partner' and Usage 'CRM'.
    <b>CIC0 of CRM 5.0 HR1</b>
    <u>Tcode: CIC0</u>
    Enter sold-to party code: 5300001 as activity partner, Contact person:244 on 'BP searching' workspace. Then on 'Maintain Business Transaction' workspace will display  5300001 as activity partner and 66 as Contact person (66 is the first contact person of sold-to party master record:5300001).
    <b><u>Configation:</u></b>
    Partner Function: 00000015 Contact person (CRM) using Access sequence 0002
    Access sequence 0002 from activity partner
    Dialog seq:10 has partner origin COM_PARTNER_A Preceding document and mark 'Allow Incorrect Source'.
    Dialog seq:20 has partner origin CRM_PARTNER_D DO NOT USE - General business partner model and have details on the source; Partner Function category '0006 Activity partner' and Usage 'CRM'.
    Dialog seq:30 has partner origin CRM_PARTNER_C Business Partner Relationship and have details on the source; Partner Function category '0006 Activity partner' and Usage 'CRM'.
    Please suggest me which access sequence should be used for getting the correct contact person (result same as CRM 2.0C).
    Thanks you so much for support.

    Hi,
    to you receive the same result also in CRMD_ORDER, or only in CIC0. Please keep in mind that there is a difference! In CIC0 no pop-ups for selecting partners is executed, so the first contact person is taken (note 487734 gives a modification. Also the partner function of ICAGENT is necessary within CIC0.
    From the view of CRMD_ORDER the following access sequence should be used:
    10     COM_PARTNER_A Preceding Document
    20     CRM_PARTNER_A BP Relationships By Sales Organization  + Wait Flag + Partner Function category '0006 Activity partner' and Usage 'CRM'.
    30     CRM_PARTNER_C Business Partner Relationships + Partner Function category '0006 Activity partner' and Usage 'CRM'.
    Hope that this information is helpful!
    Regards, Gerhard

Maybe you are looking for