Requirements for master data template

HI,
Please let me know the basic requirements for master data template. What all the infotype to be involved in collecting master data template.
Thanks and regards,
Aylwin

Hi Alwyn,
If you dealing with india payroll definately Yes subject to you business process again.
Even though it is indian payroll some item may not applicable
For exmple other income resourece will be  if you go to manufaturing industries you may face problem even though they got some they don't want reveal it to the employee.
in such that infotype is not required as per your business process.
Some states like UP there is no profession tax. Genrally we say profession tax need to be configure you need that master data.
If such case that might be wrong for that you need to give all the info
use PA30 t code go in side check what are the mandatory fields and take them as master data fields and put it in template.
If your client is able to give other field you can very well add them no harm in it.
But make sure you filled mandatory fields
That is the reason i was asking you to tell which coutry payroll you using
Best Regards

Similar Messages

  • To Understand requirement for master data

    Hi Experts,
    i am given a requirement to create a master data   and  was  asked to do below
    Extraction from r/3 for the new object ZCPAR
    Similar to ZNTORD (get key & text from 0COORDER)          
    Restricted to Order type Z040 only
    and
    Based on value of ZCPAR_ZCFAM and ZCPAR_ZCTYN                         
         update attribute ZCFAM_ZCTYN     
    How do we do that please guide .
    Thanks In Advance,
    Nitya.

    Hi Nitya,
    Just create a char infoobject ZCPAR with required Datatype & length. In the IO properties screen, you will find a tab Master data attribute/text. Just make sure that the check box "Attribute" is checked/ticked.
    Loading is same as loading any other BW DS. Just create a Infopackage & load to DS. create a Transformation from DS to MD IO ZCPAR & load the data using DTP.
    Similar to ZNTORD (get key & text from 0COORDER) Restricted to Order type Z040 only
    Similar to 1st point. Make sure both Attribute & text is checked. You can restrict for Order type either is Infopackage or you can write a small field routine in transformation like
    IF Order type EQ Z040.
    Result = 'XYZ'.
    ENDIF.
    Based on value of ZCPAR_ZCFAM and ZCPAR_ZCTYN update attribute ZCFAM_ZCTYN
    Simple field level routine for ZCFAM_ZCTYN.
    IF ZCPAR_ZCFAM EQ 'XYZ' and ZCPAR_ZCTYN EQ 'XYZ'.
    RESULT = 'XYZ'.
    ENDIF.
    Note : Replace 'XYZ' with suitable values
    Hope its clear & helpful!
    Regards,
    Pavan
    Edited by: PavanRaj_S on Dec 26, 2011 2:45 PM

  • Requirements for master

    Basic requirements for master data template.
    Infotype to be in the Indian implementation collecting master data template.
    Help me
    Thanks in avance

    Previous employer tax details
    (IT0580)     Info Type 0580 capture employees previous employment tax detail. In SAP, previous employment tax detail can be captured in Info type 0580. 
    Salary as per u/s 17 (1),Value of perquisite u/s 17 (2),  Profit in lieu of salary u/s 17 (3),  Exemptions u/s 10, Professional Tax, Provident fund, Income tax deducted, Medical exemption, Leave Encashment Exemption Amount , Gratuity Exemption Amount, LTA exemptions.     Indian specific Info types for Payroll
    House Rent Allowance
    (IT0581)     These info types capture employeeu2019s housing details. Housing (HRA / CLA/ COA). This info type captures if the employee is using own house or rented or company accommodation etc.      Indian specific Info types for Payroll
    Exemptions u2013 Subtypes
    LTA / MDA / CEA / CHA
    (IT0582)     The LTA subtype of the Exemptions Info type (0582) stores the details of the travel submitted as proof for Leave Travel Allowance (LTA) tax exemptions. The details in this subtype are used during the calculation of LTA tax exemption. This info type can be created at any point of time during a financial year. The info type records are read for the entire financial year. Each time there is a regular payroll run.
    The MDA subtype of the Exemptions Info type (0582) stores the details of the bills submitted as proofs for medical exemptions. This includes the details of proofs submitted for:
    u2022     Medical reimbursements
    u2022     Medical Insurance
    u2022     Medical reimbursement treated as insurance.
    The SCEA and SCHA subtypes of the Exemptions Info type (0582) stores the details of expenditure submitted as proofs for exemptions on child education and hostel allowances, respectively.
         Indian specific Info types for Payroll
    House Rent Allowance
    (IT0581)     These info types capture employeeu2019s housing details. Housing (HRA / CLA/ COA). This info type captures if the employee is using own house or rented or company accommodation etc.      Indian specific Info types for Payroll
    Car & Conveyance
    (IT0583)     This info type stores for an employee the details of the:
    u2022 Conveyance type
    u2022 Car and driver for the different Car Schemes     Indian specific Info types for Payroll
    Income from other sources  (IT0584)     This info type stores the details of income from sources other than that from your employment, for the current financial year.
    There are two subtypes to this info type:
    u2022     Subtype 0001 - Income From House Property
    u2022     Subtype 0002 - Income From Other Sources
         Indian specific Info types for Payroll
    Section 80 Deduction
    (IT0585)     This info type keeps a record of the proposed and actual contributions made by an employee towards Section 80 subsections and divisions.
    These info types capture employeeu2019s investment with respect to the  80CCC
    80CCC     Contribution to certain pension funds
    80D Medical Insurance Premium
    80DD Med Treatment / Depts. of handicapped dependents
    80DDB     Medical Treatment
    80E Repayment of loan for higher education
    80G Donations to certain funds, charitable .institution.
    80GG Deduction in respect of rent paid
    80GGA     Donation for Scientific/Rural Development
    80L Interest on Certain Securities/Dividends
    80RR Prof Income from Foreign Sources
    80RRA      Remuntn recvd for services rendrd abrd
    80U Permanent Physical Disability
         Indian specific Info types for Payroll
    Section 88 Deductions
    (0586)     This info type keeps a record of the proposed and actual investments made by an employee towards Section 88.     Indian specific Info types for Payroll
    Provident fund contribution (0587)     This object stores the Provident Fund information of an employee.
    This component helps you create and maintain information on employee Provident Fund. Provident Fund is a statutory contribution, and consists of two parts:
    1.     Provident Fund (PF) - Both, the employee and the employer, contribute a fixed percentage of the PF basis towards a Provident Fund. The minimum percentage contributed is as specified by the authorities.
    2.     Pension Fund - The employer contributes a fixed percentage of the PF basis towards the Pension Fund of an employee. The minimum percentage contributed is as specified by the authorities.
         Indian specific Info types for Payroll
    Other Statutory Deduction (0588)     There are three sub types to this info type:
    1.Subtype 0001 u2013 ESI Employees' State Insurance (ESI) is a benefit provided to any employee earning wages below a specified limit to provide for:
    u2022     Hospital facilities and out-patient facilities
    u2022     Medicines provided by the hospital
    u2022     Compensation in case of accident or death
    u2022     Leave subject to ESI hospitals or doctors certificate of ill-health.
    2. Sub type 0002 u2013 LWF Labour Welfare Fund (LWF) is a component of compensation provided to promote the welfare of Labour in the state. Employees who are eligible for LWF contribute a statutory amount to the LWF fund.
    3. Sub type 0003 u2013 PTX Professional Tax is a tax on employment and it is deducted from the wages payable to all employees with the exception of certain categories such as disabled and so on but may vary in different States as per the laws that govern them.
    Nominations (IT0591)     This info type stores the nomination details of employees for the following benefits:
    u2022        Employee State Insurance
    u2022        Gratuity
    u2022        Maternity Act
    u2022        Provident Fund
    u2022        Pension

  • Master data templates for Talent management

    Dear All,
    Please let me know  if someone can provide me with templates for PD.
    We are in the midst of an implementation and the employee nos are huge.
    It would take a long time for the client to complete the talent architecture and hence do not want to miss any column when I provide them with the templates.
    Templates are required for,
    1. Qualification catalog, Qualification Upload
    2. For creating Requirement profile at job and position level.
    3. For creating Skill profile at employee level and grading them
    4.Career and Development plans.
    Anything else if I have missed....
    Thanks for your help.
    Regards,
    Rijuraj

    hi
    I think thee is no seprate master data template...
    WM will use MM and SD ( customer master) master datas.
    regards
    4777

  • I need tables for prepare the master data templates for PM

    Dear Experts,
    can we prepare the master data templates by using the tables? if its possible means how we can prepare and what we have to considered ? is it right way or wrong?
    please suggest me to prepare the masterdata templates for ever use. if any small corrections we can correct it at usage time.
    please help me
    thanks a lot in advance

    Dear Jalu,
    Master data Templates have to be prepared based on Client's requirement after understanding their Business.
    For example, in Equipment master there are ~ 60 to 70 feilds, no client requires all of them. Some are inherited.
    After client requirement freezing, record LSMW and based on that prepare the Template.
    Regards,
    MLN Prasad

  • Master Data Templates for RDS

    Hello,
    Can anyone help me find the link from where i can download the Master Data template used for RDS in SAP ERP.
    the link was shown to us last month but it's gone.
    Please help.
    Thank you.
    Regards,
    Ber

    Hi Vikrant,
    I need these templates urgently. plz mail me at [email protected]
    Points will be rewaeded

  • Master Data Required for 2LIS_02_HDR Data Source Installation

    Hi All,
                  We are trying to install  2LIS_02_HDR DataSource through BC for our purchasing implementation . Can you suggest what all the Master Data required for this Data Source.
    Regards,
    Aditya

    Hi ,
    Please see this link.
    http://help.sap.com/saphelp_nw70/helpdata/en/ed/62073c44564d59e10000000a114084/frameset.htm
    http://help.sap.com/saphelp_nw70/helpdata/en/ed/62073c44564d59e10000000a114084/frameset.htm
    In the same page you can find all details.
    Hope this helps.
    Thanks
    CK

  • Help Required in Master data Data model

    Hello,
    May some one help me in explaining the relation with the sales org, sales office, sales group, distribution channel, division, plant, material, Customer, controlling area, profit centre and cost element.
    These are the info objects I have in my COPA data source. I need to decide about the master data now. I need to know which info objects can be used for master data.
    Thanks in advance!
    Help me with the inputs please!!
    Points will be assigned!
    Regards
    Sri

    <b>Sales Organization</b>
    A organizational unit in Logistics that structures the company according to its sales requirements.
    A sales organization is responsible for selling materials and services.
    <b>Sales Office</b>
    A organizational unit in a geographical area of a sales organization.
    A sales office establishes contact between the firm and the regional market.
    <b>Sales Group</b>
    A organizational unit that performs and is responsible for sales transactions.
    <b>
    Distribution Channel</b>
    CA channel through which saleable materials or services reach customers.
    Distribution channels include wholesale, retail, and direct sales. You can assign a distribution channel to one or more sales organizations.
    Please search <a href="http://help.sap.com/saphelp_nw2004s/helpdata/en/35/2cd77bd7705394e10000009b387c12/frameset.htm">Glossary</a> for more....

  • Why we are not using "Message Control" for Master data ?

    Hi friends,
    We are using Message control as output determination for Transactional data, <b>what is the main reason for not using the msg control for Master data.</b>Please explain with details...
    I am very thankful to them...
    Thanks and Regards.
    <i><b>Naveen Kumar. Chamala</b></i>

    Hi Naveen,
       Listing down those I know -
       1. Master data is expected to be changed/created less frequestly.
       2. Transactional data is expected to be chnaged/created more frequestly.
       3. Transactions to create/change/display master data do no have message control integration, since you are not supposed to print/fax/mail master data to your partners.
       4. Distribution of master data in generally supposed to happen within Enterprise boundry and typically you will have one central server maintaining master data which will be distributed to multiple downstream operation system (Some thing where MDM fits). So ideally when distributing master data using ALE you will be sending it to multiple systems.
       5. Distributing transactional data PO/SO etc is same as sending fax/print which fits with the requirement of message control.
    Hope this helps,
    Regards,
    Sanjeev

  • Overiding Mandatory Fields for master Agreement Template

    Hello,
    In the standard creation of the master agreement template the CONTACT field is mandatory. To me, this does not make sense because a template would need to be created for every contact/supplier.  We want to make the CONTACT field optional for master agreement templates.  I am trying to create a page customization with the following properties to accomplish this:
    UI ID:contracts.contract.ui.buyside.default
    Name:Master AgreementParent
    Class: Master Agreement
    Field ID: Contact
    Property: required
    Value: no
    Dimension on parent set
    Dimension Field :  IS_TEMPLATE
    Dimension Field Type: Boolean
    Dimension Value: yes
    I can not seem to make it work.  Any suggestions?  Is this even possible?
    Thanks in advance,
    Kyle

    Thanks for the quick reply.  I was hoping to avoid a dummy vendor.  This is sure a strange piece of software.
    Kyle

  • More details for master data

    Hi friends,
    I want to know more details about the master data, when there is one cube or dso, how can I find out that master data objects in that?
    When right click on master data info object and display, there is tabs called u2018general, business explorer, master data/texts, hierarchy, attribute and compoundingu2019, want to know much details on each tab and option in that.
    I know some thing about these options, but want to know all options. This is basic question, but wants to know detaily from experts. Please give more details on this. Thanks in advance.
    Suji.

    there are 6 tabs in master data datasource
    1. general tab, 2. Business explorer 3. master data/text 4. Hirarchy 5. attribute 6. Compounding
    General:
    in this there are 4 options
    1.  dictionary : give data type of that object, give length of the object, convertion rotiune is alpha which makes
    "ALPHA conversion", is a transaction (transaction code RSMDCNVEXIT) that checks the format of all values of characteristics that use one of the conversion routines ALPHA, GJAHR and NUMCV. If values are found that do not have the correct internal format it can replace them by correct value and update all dependant SAP NetWeaver BI objects (like InfoCubes, Hierarchies, master data of other characteristics...).
    The most important conversion routine - due to its common use - is the ALPHA routine that converts purely numeric user input like '4711' into '004711' (assuming that the characteristic value is 6 characters long). If a value is not purely numeric like '4711A' it is left unchanged.
    transfer routine : when u want to write the routine use the create buttom.
    Business explorer:
    use authorization relevant check box when you want the object as authorization and use in report based on user requirement.
    Master data/text:
    it shows the object has attr or text or both, you can find by identifing the check box
    Hirarchy:
    if the check box of with hierarchy is checked then it has hierarchy. 
    Attributes:
    it shows the attributes of the attributes.
    compounding:
    In Compounding, A Field or another Object is attached to an Info Object. A Compounding Characteristic is when object's definition is incomplete without the definition of another Characteristic Info Object.
    We can also determine whether we want to compound the characteristic to other InfoObjects. Sometimes we need to compound InfoObjects in order to map the data model. Some InfoObjects cannot be defined uniquely without compounding.
    For Example the Info Object - Location (0PP_LOCAT) has to be assigned with a Compound Info Object - Plant (0PLANT).
    By using compound InfoObjects, you can model the dependencies between InfoObjects. You can compound InfoObjects to map the data structure of a source system.

  • Organizational Management - LSMW & MASTER DATA TEMPLATE

    Who is responsible to upload the master data, CLIENT or CONSULTANT?
    Can someone share with us the Oragnizational Management SAMPLE LSMW TEMPLATE & MASTER DATA TEMPLATE?
    Thank you.

    Hi,
    Client will give the DATA based on the template provided by the Consultant. Upload is done by Consultant only.
    Any template can be prepared based on the fields in the screens for example infotype 0001, 0002, 0021 etc.
    Regards
    Team Member.

  • Duplicate reocrds for Master data

    Hi Friends,
    I have a request which contains duplicate records for master data. When i try to load data, after loading to PSA, BW shows an error saying that there are duplicate records.
    My requirement is still i need to load the data overwriting the previous duplicate record.
    How to do this?
    Thanks,
    Raja

    Hi,
    Subsequently i need to load the data to target as well. If i select the option "Only PSA" and "Ignore double data records" the option for "Update subsequently in data targets" is disabled.
    Thanks,
    Raja

  • Authorization for Master Data (Customer / Vendor)

    Dear All,
    I've requirement in Master Data Transaction display (XD03 / XK03), to control the dispaly of data for certain fields based on Authorization.  As an example like below...
    User X1 to see F1 & F2 data in above master transaction display data
    User X2 to see F1 field, but F2 field not authorized...should be displayed as XXX (u2018XXXu2019 u2013 means data exists in database); if data doesn't exits for field F2...then I would like to display as YYY)
    Can you please share your thoughts / ideas to implement the above requirement.
    Regds,
    Ramki.

    SAP standard does not provice such function in XD03/XK03.
    Yes, you can achieve this function using custom ABAP code but implementing in sap-standard transaction would be challanging because of the restriction on modifying sap-standard code and not having exits at right place where you would need to implement this.
    Regards,
    Pawan.

  • DTP for Master data

    Hi Guys,
    How to extract master data and hierarchies from ECC into BI infoobjects?
    Do we follow the same procedure for loading master/hierarchy data as for transaction data - i.e. Load into PSA and then create Transformations and DTPs to load into infoobjects? If so,  what is the best approach as far as Full/Delta loads.
    1. Is it ok to do a full load into PSA (using infopackage) and then do a full load always (The process chains for master data would be running nightly).
    or
    2. Should we have 2 infopackages (full and delta) into PSA and then multiple DTPs. (The process chains for master data would be running nightly).
    Regards.

    Indicator: Only Get Delta Once
    Source requests of a DTP for which this indicator is set are only transferred once, even if the DTP request is deleted in the target.
    Use
    If this indicator is set for a delta DTP, a snapshot scenario is built.
    A scenario of this type may be required if you always want an InfoProvider to contain the most up-to-date dataset for a query but the DataSource on which it is based cannot deliver a delta (new, changed or deleted data records) for technical reasons. For this type of DataSource, the current dataset for the required selection can only be transferred using a 'full update'.
    In this case, a DataStore object cannot usually be used to determine the missing delta information (overwrite and creation of delta). If this is not logically possible because, for example, data is deleted in the source without delivering reverse records, you can set this indicator and perform a snapshot scenario. Only the most up-to-date request for the DataSource is retained in the InfoProvider. Earlier requests for the DataSource are deleted from the (target) InfoProvider before a new one is requested (this is done by a process in a process chain, for example). They are not transferred again during the DTP delta process. When the system determines the delta when a new DTP is generated, these earlier (source) requests are seen as 'already fetched'.
    Setting this indicator ensures that the content of the InfoProvider is an exact representation of the source data.
    Dependencies
    Requests that need to be fetched appear with this indicator in the where-used list of the PSA request, even is they have been deleted. Instead of a traffic light you have a delete indicator.
    Get Data by Request
    This indicator belongs to a DTP that gets data from a DataSource or InfoPackage in delta mode.
    Use
    If you set this indicator, a DTP request only gets data from an individual request in the source.
    This is necessary, for example, if the dataset in the source is too large to be transferred to the target in a single request.
    Dependencies
    If you set this indicator, note that there is a risk of a backlog: If the source receives new requests faster than the DTP can fetch them, the amount of source requests to be transferred will increase steadily.

Maybe you are looking for