Documentation on assigning wagetypes to W-2

Hello All
Can anyone share any documentation on tax form groups and assigning wagetypes to W-2..
Thanks
Charlene

HI Charlene,
There is no specific document on Assignment of Wage types to W-2 Boxes. But you need to understand the relationship between Tax form group of Tax wage types and Non-Tax wage types. Accordingly assign wage types to them. Then recognize the proper Tax form field (which holds the information for W-2 boxes) and assign the Tax form group to Tax form field.
Then carry out testing in different scenarios to validate the mapping of Wage types on W-2.
Thank you,
Arti

Similar Messages

  • How can we assign Wagetypes

    Hi all,
    How can we assign wage types to Palnt.
    With Regards,
    Venu

    hi venu
    after doing the wage type please do the processing class in sm30 table name is v_512w_d see venu you are assigning here wagetypes that is not specific for a plant.  so you proceed like this
    Times Paid at an Average Rate
       Use
    Wage type ML02 is used to indicate time tickets paid according
    to
         averages in incentive wages.
    Wage Type ML01 and Wage Type ML02
    The wage type specified on a time ticket in Incentive Wages
    determines
         whether the time ticket is paid according to piecework or according to
         averages.
         The standard system uses wage type ML01 for piecework payment and
         average payment is represented by wage type ML02.
         Processing class 46 is used to distinguish between payment types
         (piecework or average) in the wage types in table T512W. In the standard
         system, the processing class has two specifications:
         o   time tickets paid according to piecework
         o   time tickets paid according to averages
         Processing class 46 has different specifications for the standard wage
         types ML01 and ML02.
    bye
    naveen

  • WCCP assignment method mismatch

    Hi all,
    I am using a Cisco 3825 running 12.4(25G) code. I just upgraded my WAE (oe674) to 5.1.1c.
    The WAE and router wouldnt peer due to assignment method mismatch when i do a show wccp router.
    Router Information for Service Id: 61
            Routers Seeing this Wide Area Engine(0)
                    -NONE-
            Routers not Seeing this Wide Area Engine
            10.204.28.1     - Assignment Method Mismatch
            Routers Notified of from other WAE's
                    -NONE-
    Router Information for Service Id: 62
            Routers Seeing this Wide Area Engine(0)
                    -NONE-
            Routers not Seeing this Wide Area Engine
            10.204.28.1     - Assignment Method Mismatch
            Routers Notified of from other WAE's
                    -NONE-
    The WAE is configured as follows:
    wccp router-list 1 10.204.28.1
    wccp tcp-promiscuous service-pair 61 62
    router-list-num 1
    assignment-method mask
    password ****
    redirect-method gre
    egress-method wccp-gre
    enable
    exit
    wccp flow-redirect enable
    When i changed the assignment method to hash, everything worked. I believe Cisco 3825 should support Mask.
    Any advice?

    Hi Leonardo,
    Did you try disabling wccp on router as well as WAE and re-enable it on router and then WAE and see if that makes a difference? If you have already done that and since as per documentation MASK assignment is supported in version you are running on router and it was working prior to upgrade, i would suggest capturing WCCP communication i.e HIA and ISU and opening a TAC case for further investigation. Did you follow the procedure as suggested in release notes during upgrade?
    WCCP Interoperability
    Central Managers running Version 5.1.1x can manage WAEs running software Versions 4.2.1 and later. However, we recommend that all WAEs in a given WCCP service group be running the same version.
    Note All WAEs in a WCCP service group must have the same mask.
    To upgrade the WAEs in your WCCP service group, follow these steps:
    Step 1 You must disable WCCP redirection on the Cisco IOS router first. To remove the global WCCP configuration, use the following no ip wccp global configuration commands:
    Router(config)# no ip wccp 61
    Router(config)# no ip wccp 62
    Step 2 Perform the WAAS software upgrade on all WAEs using the WAAS Central Manager GUI.
    Step 3 Verify that all WAEs have been upgraded in the Devices pane of the WAAS Central Manager GUI. Choose Devices to view the software version of each WAE.
    Step 4 If mask assignment is used for WCCP, ensure that all WAEs in the service group are using the same WCCP mask value.
    Step 5 Reenable WCCP redirection on the Cisco IOS routers. To enable WCCP redirection, use the ip wccp global configuration commands:
    Router(config)# ip wccp 61
    Router(config)# ip wccp 62
    Release notes for your reference.
    http://www.cisco.com/en/US/docs/app_ntwk_services/waas/waas/v511/release/notes/ws511xrn.html#wp151010
    Regards,
    Kanwal

  • Assign user to modify rules

    Hi,
    I am new to BRM. I have created and deployed a ruleset/rule/decision table. But I am not able to edit the rules in /rulesmanager.
    I am entering though the SAP_BRM_ADMIN user, but the rule is appearing read-only?
    How to assign the rules administrator to administer a particular rule?

    Hi,
    Pleaes follow this documentation to assign authorizations according to your requirement:
    http://help.sap.com/saphelp_nw73/helpdata/en/45/60a31b861e4087a2c3ac6c476184d0/frameset.htm
    Regards,
    Santosh Giri

  • CPS Job documentation

    Hi,
    In solution manager work center, after the change document is created  the job documentation is to be generated. One of the steps to create job documentation is assigning the logical component. I'm facing an issue with this step. The logical components aren't getting displayed thus the job documentation is not getting created. What could be the possible solution to this?
    Regards,
    Esha

    Hello Esha,
    if I understood your issue correctly your creating the Job Documentation from the Job Chaneg Document, so you are using the ChaRM integration?
    In that case you'll have to check IBase assigned to the Job and Change Request. The IBase has to point to a production system.
    The program also filters for logical components, which have the (logical) System, i.e. combination of System ID and Client, the IBase is pointing to, assigned in the role production.
    So you need an logical component which includes the selected system in role production.
    BTW: Please use the Solution Manager forum for JSM related questions and visit our new FAQ http://wiki.sdn.sap.com/wiki/display/SM/FAQJobScheduling+Management
    Regards,
    Martin
    Please follow us on SDN:
    http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/u/25168834 [original link is broken] [original link is broken]
    /people/martin.lauer/blog
    and SAP Service Marketplace:
    http://service.sap.com/jsm

  • Factoring based on Gross pay

    Dear Experts,
    We have a bit complex scenario regarding mid month joining and separation proration. Its like, Gross salary is reduced by the total absence amount.
    Formula is like: {Prorated Housing (Housing/30days x no.of days no worked)/Hourly Rate (Basic/195) + Total no. of hours not worked}/195 * Gross salary.
    I have been able to segregate this proration calculation of basic and housing by using factor 1 and 3 respectively and both individually has been reduced as per the formula given above i.e. Prorated Housing (Housing/30days x no.of days no worked), Hourly Rate (Basic/195 x number of hours worked).
    Now issue is how we can achieve this reduction on Gross salary scenario with our reduction factors, which is basically assigned wagetype wise in Pr.class 10.

    Hi Promod,
    Yes i can try by reducing directly /101, but issue is here, how we can achieve the reduction formula like
    {Prorated Housing (Housing/30days x no.of days not worked)/Hourly Rate (Basic/195) + Total no. of hours not worked}/195 * Gross salary.
    Prorated Housing (Housing/30days x no.of days not worked)/Hourly Rate (Basic/195)= This is basically calculating absence hours for housing + basic which is again being added with Actual absence hours.
    Please help
    Regards
    Tandrima

  • Creating support message field reported by doesn't fill

    Hi colleagues,
    When I create a support message field reported by doesn't fill automatically.
    I think that I've completed all required steps in order these fields were filled automatically. Fields sold-to party and support team are filled automatically, they work ok.
    The steps that I've checked:
    - The support message is created successfully from satellite message(SID=DES_01). The user which creates this message is zprueba5 exists with profiles: SAP_ALL, SAP_NEW at the satellite system.
    -In the solution manager system(SID=SMG), transaction ib52 for the satellite system is filled with partners: employee responsible, sold-to party and system administrator.
    - In the solution manager system(SID=SMG), zprueba5 exists with profiles: SAP_ALL, SAP_NEW.
    - Transaction bp, zprueba5 user contains BP roles: Business Partner, Employee, Bill-To Party, Financial Services and at the tab "Identification":
    External BP Number: SMG 010 ZPRUEBA5
    ID Type     Description                         Identification number
    CRM001    External System Identifier   DES_01 0020281686 100 ZPRUEBA5
    CRM001    External System Identifier   SMG 0020276689 010 ZPRUEBA5
    So, In the solution manager system(SID=SMG), crm_dno_monitor transaction when I open the support message just created from satellite system, I have an error because reported by field isn't filled.
    Please could you help me?
    Thanks and Regards
    Raul Aguilar

    Hi Nikhil,
    At this message I'm going to reply your last two replies.
    1.- You typed me "In ib52 select both the system simultaneously and then go to->parner and assign proper bp no for the respective partner function. You need to do it for every system may be users are same.
    I hope you have maintained proper access sequence i.e. via ibase."
    For each SAP System that I've defined at SAP Solution Manager, at ib52 transaction I've defined the three roles that IMG activity documentation types:
            Assign business partners with the following functions to the new iBase component systems:
                Administrator
                Key User
                Sold-to Party
    SAP Solution Manager Implementation Guide->SAP Solution Manager(SP 17)->Configuration->Basic Settings->Standard Configuration of Basic Settings->Solution Manager->iBase->Assign Business Partners to iBase Components ->transaction Change iBase (IB52), enter in field Installed Base '1' and I select the SAP System->Goto -> Partner
          Function                                        Partner      
        00000014  Employee Responsible     298
        00000001  Sold-To Party                  295
        SLFN0001 System Administrator      295
    2.- You typed me  "Select you partner determination procedure and double click on "User interface setting" here select appropriate partner functions and assign all of them in ibase as I said in above reply.
    You must not be getting reported by partner function. Take out System administrator. Motivate by assigning points."
    My Partner Determ. Proc. is SLFN0001, so I double click on User interface setting like you explained me, adn now appears:
    Header Screen:
    Sequence and Functions for (main) Partner Displayed
    Partner Function1 00000001  Sold-To Party (CRM)
    Partner Function2 SLFN0002 Reported by (CRM)
    Partner Function3 SLFN0003 Support Team (CRM)
    Partner Function4 SLFN0004 Message Processor (CRM)
    But now I don't understand if at ib52 transaction I've to add any role or if from "User interface setting" I've to delete any Partner Function. Could you detail me when you type "You must not be getting reported by partner function. Take out System administrator", please?
    Regards,
    Raul .

  • How to upload many Files in the table of Project Document (Solution Man)  ?

    I have generate some hundreed  PDF-Files and I want to upload this PDF files in the table of  Project Documentation in the Solution Manager.
    In the Solution Manager is it only possible to upload this files single.
    My intention is  to write an abap program that upload all files automatically in this Project Documentation and assign this documents in the right  project.
    Which tables are used in this context ?
    Where I can find the assignment  between documents and projects  in se16, in wich table ?
    Is existing an introduction document to this topic, where i can get more information ?
    Thank you in advance.

    GerdW wrote:
    Hi dimitriev,
    Target: I have a array of cluster in my project in main VI and have lots of VIs which uses this array via reference as global variable.
    When accessing that array from a lot of locations simultanously you will get RACE CONDITIONS. Easily and fast…
    Use a FGV aka AE instead to encapsulate your "data object"!
    Another good option sounds like the Data Value Reference.  Those work really well if you want to keep a reference to pass around to everybody.
    There are only two ways to tell somebody thanks: Kudos and Marked Solutions
    Unofficial Forum Rules and Guidelines

  • How to configure Pay Roll in SAP

    Dear Gurus,
    How to configure Pay Roll in SAP. Pls suggest.
    Regards
    Pankaj
    Please have a look at the forum search

    Define Employee Sub Group Grouping for PCR and CAP    / Check Payscale Area   / Check Payscale Type  / Check Assignment of Pay Scale Structure to Enterprise Structure  / TARIF Feature / Create Control Record / Revise Payscale groups and levels /  Create Wage type catalog /  Employee Subgroup Grouping for primary wage types / Personnel Subarea Grouping for Primary Wage Type / Setup Payroll Period for Collective Agreement Provision / Check wage type group Basic pay / Define wage type permissibility for each PS and ESG / Check wage type characteristics / Maintain Valuation of Base Wage types /
    Check Wage Type Group Recurring Payments and Deductions / Check Wage Type Group Additional Payments /Check Wage Type Group Membership Fees / Membership Payee /Determine allowed payees per membership type /Define Membership / Deduction Types /Define Trust Details for Provident Fund /Maintain Contribution Details for Provident Fund ( Feature 40EPF )
    Assign Company Rates for Provident Fund / Define PF Trust Validity Period / Define Contribution type for Statutory rates for Provident Fund /Maintain ESI Eligibility Limit /  Define Personnel Area and Subarea Groupings for ESI /Assign ESI Groupings for Personnel Area and Subarea/
    Maintain Contribution Rates for ESI/
    Maintain Gratuity Trust ID/
    Maintain Gratuity Contribution Frequency and related wage types/
    Define Contribution Rates for Gratuity/
    Maintain Superannuation Trust ID/
    Maintain Superannuation Contrib. Freq and Rel. Wage Types/
    Define Contribution Rates for Superannuation/
    Maintain Loan Types/
    Create Loan Conditions/
    Maintain Loans Grouping  (Feature 40LGR)/
    Maintain Salary Components ( Feature 40LSL)/
    Max. no. loans allowed (LML1)( Maximum number of loans allowed at a time)/
    Max. no. loans allowed (LML2)(Maximum no of loans allowed)/
    Maintain Maximum amount for loans outstanding(LMVAL)/
    Maintain Loans Eligibility Checks and Limits/
    Maintain Accommodation Types/
    Maintain the processing options for CLA/
    Define Conveyance Types/
    Assign eligibility criteria for conveyance allowance/
    Define Professional Tax Grouping Details/
    Assign Professional Tax Groupings for Personnel Areas and Subareas/
    Assign Amounts for Professional Tax Deduction/
    Maintain Method and Form Layout for Professional Tax Groupings/
    Define Personnel Area and Subarea Groupings for Tax/
    Assign Tax Groupings for Personnel Areas and Subareas/
    Define Tax Codes/
    Assign Tax Code Limits to Wage Types/
    Assign wagetype to wagetype group offcycle /
    Set Up Off-Cycle Reasons/
    Specify default values for wage types Off Cycle/
    Specify Default Values for Payment Methods/
    Configure wage types for Section 80/
    Configure wage types for Section 88/
    Define other allowance or re-imbursement type for exemption/
    Define priority for  deductions/
    Maintain recovery of arrears/
    Define cumulation types for wage types/
    Assign universal contribution groupings for universal contribution types /
    Assign state for universal contribution grouping/
    Assign slab code and other parameters for each state of univ.type./
    Assign Contribution value for each slab./
    Define Period Parameters/
    Define Date Modifiers/
    Check Payroll Accounting Area/
    Generate Payroll Periods/
    Generate calendar for cummulation/
    Assign Basic Wage Types to Grouping for Allowances/
    Define Pay scale groupings for Allowance/
    Assign Pay Scale Groupings for Allowances/
    Assign wage type model for Pay scale grouping for Allowances/
    Calculate Eligibility for Raps/ . ....................................................................................................................................................................................................................................................................
    If you get the knowledge then please .  mark the questions as answered

  • XPath Expression in document definition

    I am trying to use "XPath Expression1" for 894 in the document definition under XPath in order to retrieve invoice number so that, it would be used in BAM but I am not getting successful in putting exact XPath expression for invoice number. I am using as below
    /Transaction-894/Segment-G82/Element-861
    Pls suggest is there any wrong in the XPath?
    Regards,
    Suneel Jakka

    Here is the XSD for which I am trying XPath for the "Element-861" under "Segment-G82"..
    Pls suggest me..
    <?xml version="1.0" encoding="UTF-8"?>
    <!-- Automatically generated by EDIFECS SpecBuilder (http://www.edifecs.com) -->
    <xsd:schema xmlns="http://www.edifecs.com/xdata/200" targetNamespace="http://www.edifecs.com/xdata/200" xmlns:xsd="http://www.w3.org/2001/XMLSchema" version="1.0" elementFormDefault="qualified">
         <xsd:annotation>
              <xsd:appinfo>
                   <FileName>C:\Documents and Settings\jakkasun\Desktop\11g\X12_5010_894.ecs</FileName>
                   <InternalID>{0840BE5F-3518-463D-A128-D73D96D4A5D2}</InternalID>
              </xsd:appinfo>
         </xsd:annotation>
         <xsd:element name="Transaction-894" type="Transaction-894"/>
         <xsd:complexType name="Transaction-894">
              <xsd:annotation>
                   <xsd:documentation>This X12 Transaction Set contains the format and establishes the data contents of the Delivery/Return Base Record Transaction Set (894) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to enable a Direct Store Delivery (DSD) vendor to communicate the details of a DSD delivery and is to be used during the check-in procedure. </xsd:documentation>
                   <xsd:appinfo>
                        <UNMKey>Full|CodeList|-&lt;Parent Node ID&gt;.&lt;Index&gt;|Composite|-&lt;Node ID&gt;|Element|-&lt;Node ID&gt;|Loop|-&lt;Node ID&gt;|Segment|-&lt;Node ID&gt;|Transaction|-&lt;Node ID&gt;|ReplacementCharacter|_|InternalSeparator|-</UNMKey>
                   </xsd:appinfo>
              </xsd:annotation>
              <xsd:sequence>
                   <xsd:element name="Internal-Properties" type="Internal-Properties" minOccurs="0"/>
                   <xsd:element name="Segment-ST" type="Segment-ST"/>
                   <xsd:element name="Segment-G82" type="Segment-G82"/>
                   <xsd:element name="Segment-N9" type="Segment-N9" minOccurs="0" maxOccurs="unbounded" nillable="true"/>
                   <xsd:element name="Loop-LS" type="Loop-LS" minOccurs="0" nillable="true"/>
                   <xsd:element name="Segment-G72" type="Segment-G72" minOccurs="0" maxOccurs="20" nillable="true"/>
                   <xsd:element name="Segment-G23" type="Segment-G23" minOccurs="0" maxOccurs="20" nillable="true"/>
                   <xsd:element name="Segment-G84" type="Segment-G84"/>
                   <xsd:element name="Segment-G86" type="Segment-G86"/>
                   <xsd:element name="Segment-G85" type="Segment-G85"/>
                   <xsd:element name="Segment-SE" type="Segment-SE"/>
              </xsd:sequence>
              <xsd:attribute name="Type" default="Transaction" type="xsd:string"/>
              <xsd:attribute name="ID" default="894" type="xsd:string"/>
              <xsd:attribute name="Name" default="Delivery/Return Base Record" type="xsd:string"/>
              <xsd:attribute name="XDataVersion" fixed="2.0" type="xsd:string"/>
              <xsd:attribute name="Standard" fixed="X12" use="required" type="xsd:string"/>
              <xsd:attribute name="Version" default="V5010" type="xsd:string"/>
              <xsd:attribute name="GUID" type="GUID"/>
              <xsd:attribute name="CreatedBy" type="xsd:string"/>
              <xsd:attribute name="CreatedDate" type="xsd:dateTime"/>
         </xsd:complexType>
         <xsd:simpleType name="GUID">
              <xsd:restriction base="xsd:string">
                   <xsd:pattern value="\{[a-fA-F0-9]{8}-[a-fA-F0-9]{4}-[a-fA-F0-9]{4}-[a-fA-F0-9]{4}-[a-fA-F0-9]{12}\}"/>
              </xsd:restriction>
         </xsd:simpleType>
         <xsd:complexType name="EDI-Element-String-Type">
              <xsd:simpleContent>
                   <xsd:extension base="xsd:string">
                        <xsd:attribute name="Type" default="Element" type="xsd:string"/>
                        <xsd:attribute name="EDIDataType" type="xsd:string"/>
                        <xsd:attribute name="Macro" type="xsd:string" use="optional"/>
                        <xsd:attribute name="ApplicationInfo" type="xsd:string"/>
                        <xsd:attribute name="ID" type="xsd:string"/>
                        <xsd:attribute name="Name" type="xsd:string"/>
                   </xsd:extension>
              </xsd:simpleContent>
         </xsd:complexType>
         <xsd:complexType name="EDI-Element-Integer-Type">
              <xsd:simpleContent>
                   <xsd:extension base="xsd:integer">
                        <xsd:attribute name="Type" default="Element" type="xsd:string"/>
                        <xsd:attribute name="EDIDataType" type="xsd:string"/>
                        <xsd:attribute name="Macro" type="xsd:string" use="optional"/>
                        <xsd:attribute name="ApplicationInfo" type="xsd:string"/>
                        <xsd:attribute name="ID" type="xsd:string"/>
                        <xsd:attribute name="Name" type="xsd:string"/>
                   </xsd:extension>
              </xsd:simpleContent>
         </xsd:complexType>
         <xsd:complexType name="EDI-Element-Decimal-Type">
              <xsd:simpleContent>
                   <xsd:extension base="xsd:decimal">
                        <xsd:attribute name="Type" default="Element" type="xsd:string"/>
                        <xsd:attribute name="EDIDataType" type="xsd:string"/>
                        <xsd:attribute name="Macro" type="xsd:string" use="optional"/>
                        <xsd:attribute name="ApplicationInfo" type="xsd:string"/>
                        <xsd:attribute name="ID" type="xsd:string"/>
                        <xsd:attribute name="Name" type="xsd:string"/>
                   </xsd:extension>
              </xsd:simpleContent>
         </xsd:complexType>
         <xsd:complexType name="EDI-Element-hexBinary-Type">
              <xsd:simpleContent>
                   <xsd:extension base="xsd:hexBinary">
                        <xsd:attribute name="Type" default="Element" type="xsd:string"/>
                        <xsd:attribute name="EDIDataType" type="xsd:string"/>
                        <xsd:attribute name="Macro" type="xsd:string" use="optional"/>
                        <xsd:attribute name="ApplicationInfo" type="xsd:string"/>
                        <xsd:attribute name="ID" type="xsd:string"/>
                        <xsd:attribute name="Name" type="xsd:string"/>
                   </xsd:extension>
              </xsd:simpleContent>
         </xsd:complexType>
         <xsd:complexType name="EDI-Element-base64Binary-Type">
              <xsd:simpleContent>
                   <xsd:extension base="xsd:base64Binary">
                        <xsd:attribute name="Type" default="Element" type="xsd:string"/>
                        <xsd:attribute name="EDIDataType" type="xsd:string"/>
                        <xsd:attribute name="Macro" type="xsd:string" use="optional"/>
                        <xsd:attribute name="ApplicationInfo" type="xsd:string"/>
                        <xsd:attribute name="ID" type="xsd:string"/>
                        <xsd:attribute name="Name" type="xsd:string"/>
                   </xsd:extension>
              </xsd:simpleContent>
         </xsd:complexType>
         <xsd:complexType name="EDI-Element-Any-Type">
              <xsd:simpleContent>
                   <xsd:extension base="xsd:string">
                        <xsd:attribute name="Type" default="Element" type="xsd:string"/>
                        <xsd:attribute name="EDIDataType" type="xsd:string"/>
                        <xsd:attribute name="Macro" type="xsd:string" use="optional"/>
                        <xsd:attribute name="ApplicationInfo" type="xsd:string"/>
                        <xsd:attribute name="ID" type="xsd:string"/>
                        <xsd:attribute name="Name" type="xsd:string"/>
                   </xsd:extension>
              </xsd:simpleContent>
         </xsd:complexType>
         <xsd:complexType name="Internal-Properties">
              <xsd:sequence>
                   <xsd:element name="Data-Structure" type="Data-Structure" minOccurs="0" maxOccurs="unbounded"/>
              </xsd:sequence>
         </xsd:complexType>
         <xsd:complexType name="Data-Structure">
              <xsd:sequence>
                   <xsd:element name="Lookup" type="Lookup" minOccurs="0" maxOccurs="unbounded"/>
                   <xsd:element name="Property" type="Property" minOccurs="0" maxOccurs="unbounded"/>
                   <xsd:element name="Data-Structure" type="Data-Structure" minOccurs="0" maxOccurs="unbounded"/>
              </xsd:sequence>
              <xsd:attribute name="Name" type="xsd:string"/>
              <xsd:attribute name="GUID" type="GUID"/>
         </xsd:complexType>
         <xsd:complexType name="Lookup">
              <xsd:simpleContent>
                   <xsd:extension base="xsd:string">
                        <xsd:attribute name="Name" type="xsd:string"/>
                   </xsd:extension>
              </xsd:simpleContent>
         </xsd:complexType>
         <xsd:complexType name="Property">
              <xsd:simpleContent>
                   <xsd:extension base="xsd:string">
                        <xsd:attribute name="Name" type="xsd:string"/>
                   </xsd:extension>
              </xsd:simpleContent>
         </xsd:complexType>
         <xsd:complexType name="Segment-ST">
              <xsd:annotation>
                   <xsd:documentation>To indicate the start of a transaction set and to assign a control number</xsd:documentation>
              </xsd:annotation>
              <xsd:sequence>
                   <xsd:element name="Element-143" type="Element-143"/>
                   <xsd:element name="Element-329" type="Element-329"/>
                   <xsd:element name="Element-1705" type="Element-1705" minOccurs="0" nillable="true"/>
              </xsd:sequence>
              <xsd:attribute name="Type" default="Segment" type="xsd:string"/>
              <xsd:attribute name="ID" default="ST" type="xsd:string"/>
              <xsd:attribute name="Name" default="Transaction Set Header" type="xsd:string"/>
         </xsd:complexType>
         <xsd:complexType name="Element-143">
              <xsd:annotation>
                   <xsd:documentation>Code uniquely identifying a Transaction Set </xsd:documentation>
              </xsd:annotation>
              <xsd:simpleContent>
                   <xsd:restriction base="EDI-Element-String-Type">
                        <xsd:enumeration value="100"/>
                        <xsd:enumeration value="101"/>
                        <xsd:enumeration value="102"/>
                        <xsd:enumeration value="103"/>
                        <xsd:enumeration value="104"/>
                        <xsd:enumeration value="105"/>
                        <xsd:enumeration value="106"/>
                        <xsd:enumeration value="107"/>
                        <xsd:enumeration value="108"/>
                        <xsd:enumeration value="109"/>
                        <xsd:enumeration value="110"/>
                        <xsd:enumeration value="111"/>
                        <xsd:enumeration value="112"/>
                        <xsd:enumeration value="113"/>
                        <xsd:enumeration value="120"/>
                        <xsd:enumeration value="121"/>
                        <xsd:enumeration value="124"/>
                        <xsd:enumeration value="125"/>
                        <xsd:enumeration value="126"/>
                        <xsd:enumeration value="127"/>
                        <xsd:enumeration value="128"/>
                        <xsd:enumeration value="129"/>
                        <xsd:enumeration value="130"/>
                        <xsd:enumeration value="131"/>
                        <xsd:enumeration value="132"/>
                        <xsd:enumeration value="133"/>
                        <xsd:enumeration value="135"/>
                        <xsd:enumeration value="138"/>
                        <xsd:enumeration value="139"/>
                        <xsd:enumeration value="140"/>
                        <xsd:enumeration value="141"/>
                        <xsd:enumeration value="142"/>
                        <xsd:enumeration value="143"/>
                        <xsd:enumeration value="144"/>
                        <xsd:enumeration value="146"/>
                        <xsd:enumeration value="147"/>
                        <xsd:enumeration value="148"/>
                        <xsd:enumeration value="149"/>
                        <xsd:enumeration value="150"/>
                        <xsd:enumeration value="151"/>
                        <xsd:enumeration value="152"/>
                        <xsd:enumeration value="153"/>
                        <xsd:enumeration value="154"/>
                        <xsd:enumeration value="155"/>
                        <xsd:enumeration value="157"/>
                        <xsd:enumeration value="158"/>
                        <xsd:enumeration value="159"/>
                        <xsd:enumeration value="160"/>
                        <xsd:enumeration value="161"/>
                        <xsd:enumeration value="163"/>
                        <xsd:enumeration value="170"/>
                        <xsd:enumeration value="175"/>
                        <xsd:enumeration value="176"/>
                        <xsd:enumeration value="179"/>
                        <xsd:enumeration value="180"/>
                        <xsd:enumeration value="185"/>
                        <xsd:enumeration value="186"/>
                        <xsd:enumeration value="187"/>
                        <xsd:enumeration value="188"/>
                        <xsd:enumeration value="189"/>
                        <xsd:enumeration value="190"/>
                        <xsd:enumeration value="191"/>
                        <xsd:enumeration value="194"/>
                        <xsd:enumeration value="195"/>
                        <xsd:enumeration value="196"/>
                        <xsd:enumeration value="197"/>
                        <xsd:enumeration value="198"/>
                        <xsd:enumeration value="199"/>
                        <xsd:enumeration value="200"/>
                        <xsd:enumeration value="201"/>
                        <xsd:enumeration value="202"/>
                        <xsd:enumeration value="203"/>
                        <xsd:enumeration value="204"/>
                        <xsd:enumeration value="205"/>
                        <xsd:enumeration value="206"/>
                        <xsd:enumeration value="210"/>
                        <xsd:enumeration value="211"/>
                        <xsd:enumeration value="212"/>
                        <xsd:enumeration value="213"/>
                        <xsd:enumeration value="214"/>
                        <xsd:enumeration value="215"/>
                        <xsd:enumeration value="216"/>
                        <xsd:enumeration value="217"/>
                        <xsd:enumeration value="219"/>
                        <xsd:enumeration value="220"/>
                        <xsd:enumeration value="222"/>
                        <xsd:enumeration value="223"/>
                        <xsd:enumeration value="224"/>
                        <xsd:enumeration value="225"/>
                        <xsd:enumeration value="227"/>
                        <xsd:enumeration value="228"/>
                        <xsd:enumeration value="240"/>
                        <xsd:enumeration value="242"/>
                        <xsd:enumeration value="244"/>
                        <xsd:enumeration value="245"/>
                        <xsd:enumeration value="248"/>
                        <xsd:enumeration value="249"/>
                        <xsd:enumeration value="250"/>
                        <xsd:enumeration value="251"/>
                        <xsd:enumeration value="252"/>
                        <xsd:enumeration value="255"/>
                        <xsd:enumeration value="256"/>
                        <xsd:enumeration value="259"/>
                        <xsd:enumeration value="260"/>
                        <xsd:enumeration value="261"/>
                        <xsd:enumeration value="262"/>
                        <xsd:enumeration value="263"/>
                        <xsd:enumeration value="264"/>
                        <xsd:enumeration value="265"/>
                        <xsd:enumeration value="266"/>
                        <xsd:enumeration value="267"/>
                        <xsd:enumeration value="268"/>
                        <xsd:enumeration value="269"/>
                        <xsd:enumeration value="270"/>
                        <xsd:enumeration value="271"/>
                        <xsd:enumeration value="272"/>
                        <xsd:enumeration value="273"/>
                        <xsd:enumeration value="274"/>
                        <xsd:enumeration value="275"/>
                        <xsd:enumeration value="276"/>
                        <xsd:enumeration value="277"/>
                        <xsd:enumeration value="278"/>
                        <xsd:enumeration value="280"/>
                        <xsd:enumeration value="283"/>
                        <xsd:enumeration value="284"/>
                        <xsd:enumeration value="285"/>
                        <xsd:enumeration value="286"/>
                        <xsd:enumeration value="288"/>
                        <xsd:enumeration value="290"/>
                        <xsd:enumeration value="300"/>
                        <xsd:enumeration value="301"/>
                        <xsd:enumeration value="303"/>
                        <xsd:enumeration value="304"/>
                        <xsd:enumeration value="309"/>
                        <xsd:enumeration value="310"/>
                        <xsd:enumeration value="311"/>
                        <xsd:enumeration value="312"/>
                        <xsd:enumeration value="313"/>
                        <xsd:enumeration value="315"/>
                        <xsd:enumeration value="317"/>
                        <xsd:enumeration value="319"/>
                        <xsd:enumeration value="322"/>
                        <xsd:enumeration value="323"/>
                        <xsd:enumeration value="324"/>
                        <xsd:enumeration value="325"/>
                        <xsd:enumeration value="326"/>
                        <xsd:enumeration value="350"/>
                        <xsd:enumeration value="352"/>
                        <xsd:enumeration value="353"/>
                        <xsd:enumeration value="354"/>
                        <xsd:enumeration value="355"/>
                        <xsd:enumeration value="356"/>
                        <xsd:enumeration value="357"/>
                        <xsd:enumeration value="358"/>
                        <xsd:enumeration value="361"/>
                        <xsd:enumeration value="362"/>
                        <xsd:enumeration value="404"/>
                        <xsd:enumeration value="410"/>
                        <xsd:enumeration value="412"/>
                        <xsd:enumeration value="414"/>
                        <xsd:enumeration value="417"/>
                        <xsd:enumeration value="418"/>
                        <xsd:enumeration value="419"/>
                        <xsd:enumeration value="420"/>
                        <xsd:enumeration value="421"/>
                        <xsd:enumeration value="422"/>
                        <xsd:enumeration value="423"/>
                        <xsd:enumeration value="424"/>
                        <xsd:enumeration value="425"/>
                        <xsd:enumeration value="426"/>
                        <xsd:enumeration value="429"/>
                        <xsd:enumeration value="431"/>
                        <xsd:enumeration value="432"/>
                        <xsd:enumeration value="433"/>
                        <xsd:enumeration value="434"/>
                        <xsd:enumeration value="435"/>
                        <xsd:enumeration value="436"/>
                        <xsd:enumeration value="437"/>
                        <xsd:enumeration value="440"/>
                        <xsd:enumeration value="451"/>
                        <xsd:enumeration value="452"/>
                        <xsd:enumeration value="453"/>
                        <xsd:enumeration value="455"/>
                        <xsd:enumeration value="456"/>
                        <xsd:enumeration value="460"/>
                        <xsd:enumeration value="463"/>
                        <xsd:enumeration value="466"/>
                        <xsd:enumeration value="468"/>
                        <xsd:enumeration value="470"/>
                        <xsd:enumeration value="475"/>
                        <xsd:enumeration value="485"/>
                        <xsd:enumeration value="486"/>
                        <xsd:enumeration value="490"/>
                        <xsd:enumeration value="492"/>
                        <xsd:enumeration value="494"/>
                        <xsd:enumeration value="500"/>
                        <xsd:enumeration value="501"/>
                        <xsd:enumeration value="503"/>
                        <xsd:enumeration value="504"/>
                        <xsd:enumeration value="511"/>
                        <xsd:enumeration value="517"/>
                        <xsd:enumeration value="521"/>
                        <xsd:enumeration value="527"/>
                        <xsd:enumeration value="536"/>
                        <xsd:enumeration value="540"/>
                        <xsd:enumeration value="561"/>
                        <xsd:enumeration value="567"/>
                        <xsd:enumeration value="568"/>
                        <xsd:enumeration value="601"/>
                        <xsd:enumeration value="602"/>
                        <xsd:enumeration value="620"/>
                        <xsd:enumeration value="625"/>
                        <xsd:enumeration value="650"/>
                        <xsd:enumeration value="715"/>
                        <xsd:enumeration value="753"/>
                        <xsd:enumeration value="754"/>
                        <xsd:enumeration value="805"/>
                        <xsd:enumeration value="806"/>
                        <xsd:enumeration value="810"/>
                        <xsd:enumeration value="811"/>
                        <xsd:enumeration value="812"/>
                        <xsd:enumeration value="813"/>
                        <xsd:enumeration value="814"/>
                        <xsd:enumeration value="815"/>
                        <xsd:enumeration value="816"/>
                        <xsd:enumeration value="818"/>
                        <xsd:enumeration value="819"/>
                        <xsd:enumeration value="820"/>
                        <xsd:enumeration value="821"/>
                        <xsd:enumeration value="822"/>
                        <xsd:enumeration value="823"/>
                        <xsd:enumeration value="824"/>
                        <xsd:enumeration value="826"/>
                        <xsd:enumeration value="827"/>
                        <xsd:enumeration value="828"/>
                        <xsd:enumeration value="829"/>
                        <xsd:enumeration value="830"/>
                        <xsd:enumeration value="831"/>
                        <xsd:enumeration value="832"/>
                        <xsd:enumeration value="833"/>
                        <xsd:enumeration value="834"/>
                        <xsd:enumeration value="835"/>
                        <xsd:enumeration value="836"/>
                        <xsd:enumeration value="837"/>
                        <xsd:enumeration value="838"/>
                        <xsd:enumeration value="839"/>
                        <xsd:enumeration value="840"/>
                        <xsd:enumeration value="841"/>
                        <xsd:enumeration value="842"/>
                        <xsd:enumeration value="843"/>
                        <xsd:enumeration value="844"/>
                        <xsd:enumeration value="845"/>
                        <xsd:enumeration value="846"/>
                        <xsd:enumeration value="847"/>
                        <xsd:enumeration value="848"/>
                        <xsd:enumeration value="849"/>
                        <xsd:enumeration value="850"/>
                        <xsd:enumeration value="851"/>
                        <xsd:enumeration value="852"/>
                        <xsd:enumeration value="853"/>
                        <xsd:enumeration value="854"/>
                        <xsd:enumeration value="855"/>
                        <xsd:enumeration value="856"/>
                        <xsd:enumeration value="857"/>
                        <xsd:enumeration value="858"/>
                        <xsd:enumeration value="859"/>
                        <xsd:enumeration value="860"/>
                        <xsd:enumeration value="861"/>
                        <xsd:enumeration value="862"/>
                        <xsd:enumeration value="863"/>
                        <xsd:enumeration value="864"/>
                        <xsd:enumeration value="865"/>
                        <xsd:enumeration value="866"/>
                        <xsd:enumeration value="867"/>
                        <xsd:enumeration value="868"/>
                        <xsd:enumeration value="869"/>
                        <xsd:enumeration value="870"/>
                        <xsd:enumeration value="871"/>
                        <xsd:enumeration value="872"/>
                        <xsd:enumeration value="873"/>
                        <xsd:enumeration value="874"/>
                        <xsd:enumeration value="875"/>
                        <xsd:enumeration value="876"/>
                        <xsd:enumeration value="877"/>
                        <xsd:enumeration value="878"/>
                        <xsd:enumeration value="879"/>
                        <xsd:enumeration value="880"/>
                        <xsd:enumeration value="881"/>
                        <xsd:enumeration value="882"/>
                        <xsd:enumeration value="883"/>
                        <xsd:enumeration value="884"/>
                        <xsd:enumeration value="885"/>
                        <xsd:enumeration value="886"/>
                        <xsd:enumeration value="887"/>
                        <xsd:enumeration value="888"/>
                        <xsd:enumeration value="889"/>
                        <xsd:enumeration value="891"/>
                        <xsd:enumeration value="893"/>
                        <xsd:enumeration value="894"/>
                        <xsd:enumeration value="895"/>
                        <xsd:enumeration value="896"/>
                        <xsd:enumeration value="920"/>
                        <xsd:enumeration value="924"/>
                        <xsd:enumeration value="925"/>
                        <xsd:enumeration value="926"/>
                        <xsd:enumeration value="928"/>
                        <xsd:enumeration value="940"/>
                        <xsd:enumeration value="943"/>
                        <xsd:enumeration value="944"/>
                        <xsd:enumeration value="945"/>
                        <xsd:enumeration value="947"/>
                        <xsd:enumeration value="980"/>
                        <xsd:enumeration value="990"/>
                        <xsd:enumeration value="993"/>
                        <xsd:enumeration value="996"/>
                        <xsd:enumeration value="997"/>
                        <xsd:enumeration value="998"/>
                        <xsd:enumeration value="999"/>
                        <xsd:attribute name="EDIDataType" fixed="ID" type="xsd:string"/>
                        <xsd:attribute name="ID" fixed="143" type="xsd:string"/>
                        <xsd:attribute name="Name" fixed="Transaction Set Identifier Code" type="xsd:string"/>
                   </xsd:restriction>
              </xsd:simpleContent>
         </xsd:complexType>
         <xsd:complexType name="Element-329">
              <xsd:annotation>
                   <xsd:documentation>Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set </xsd:documentation>
              </xsd:annotation>
              <xsd:simpleContent>
                   <xsd:restriction base="EDI-Element-String-Type">
                        <xsd:minLength value="4"/>
                        <xsd:maxLength value="9"/>
                        <xsd:attribute name="EDIDataType" fixed="AN" type="xsd:string"/>
                        <xsd:attribute name="ID" fixed="329" type="xsd:string"/>
                        <xsd:attribute name="Name" fixed="Transaction Set Control Number" type="xsd:string"/>
                   </xsd:restriction>
              </xsd:simpleContent>
         </xsd:complexType>
         <xsd:complexType name="Element-1705">
              <xsd:annotation>
                   <xsd:documentation>Reference assigned to identify Implementation Convention </xsd:documentation>
              </xsd:annotation>
              <xsd:simpleContent>
                   <xsd:restriction base="EDI-Element-String-Type">
                        <xsd:minLength value="1"/>
                        <xsd:maxLength value="35"/>
                        <xsd:attribute name="EDIDataType" fixed="AN" type="xsd:string"/>
                        <xsd:attribute name="ID" fixed="1705" type="xsd:string"/>
                        <xsd:attribute name="Name" fixed="Implementation Convention Reference" type="xsd:string"/>
                   </xsd:restriction>
              </xsd:simpleContent>
         </xsd:complexType>
         <xsd:complexType name="Segment-G82">
              <xsd:annotation>
                   <xsd:documentation>To transmit identifying numbers, dates, and other basic data relating to the transaction set</xsd:documentation>
              </xsd:annotation>
              <xsd:sequence>
                   <xsd:element name="Element-478" type="Element-478"/>
                   <xsd:element name="Element-861" type="Element-861"/>
                   <xsd:element name="Element-860" type="Element-860"/>
    Regards,
    Suneel Jakka

  • Templates in Tcode SOLAR_PROJECT_ADMIN

    Hi!
    I would like to use the templates from Tcode SOLAR_PROJECT_ADMIN --> Project --> Projectstandards --> Documentation types --> Project templates
    for the documents in Tcode SOLAR01, SOLAR02.
    The problem is that many of them are empty.
    <b>How can I use the  templates with content?
    Is there some integrated Knowledge management system?</b>
    Thank you
    regards

    Axel
    SAP only provides you with some templates.  Not all of the documentation types have templates assign to it & that is why it is "empty". 
    You can assign your own company-specific document templates to the existing document types or alternatively create new documentation types & assign the templates there.
    Then ensure that these documentation types are assigned to your project so that it is accessible in SOLAR01/SOLAR02.
    Regards
    Danell

  • Oracle 10g R2 RAC - IP address Change

    We succsessfully installed Oracle 10gR2 single database on two node RAC on Windows 2003. I followed the Oracle RAC installation documentation and assigned a public IP for the machine and another Virtual Public IP and a Private IP. We have also changed the "hosts" file in Windows to reflect the above mentioned confiuration. Here is a snippet of the "hosts" file in Windows.
    xxx.xxx.xx.xxx NODE1
    xxx.xxx.xx.xxx NODE1-VIP
    192.168.1.161 NODE1-PRIV
    xxx.xxx.xx.xxx NODE2
    xxx.xxx.xx.xxx NODE2-VIP
    192.168.1.161 NODE2-PRIV
    After succsessful installation and testing for a few days, we are in a situation where we need to chanage the public IP's for NODE1-VIP and NODE2-VIP. If I change the IP's in the "hosts" file for NODE1-VIP and NODE2-VIP and restart the computer, both the nodes are not starting up and it comes back with a windows error. But If I change back to the old IP's, it works absolutely fine. How can we change the Virtual IP's associated for each node after a successful RAC installation?
    Thanks.

    Hi,
    The VIP are registered as a highly available resource within the Oracle Cluster Registry (OCR).
    If you want to use different VIP's than the previously configured you need this Metalink Note: 271121.1 - How to change VIP and VIP/Hostname in 10g
    Be aware of the following bug: 4500688 - THE INTERFACE NAME SHOULD BE SPECIFY WHEN EXECUTING 'SRVCTL MODIFY NODEAPPS' that is not described in the mentioned Metalink note above. This means that it is better idea to modify the VIPs by explicitly specifying the network interface name, for instance: srvctl modify nodeapps -n mynode1 -A 100.200.300.40/255.255.255.0/eth0
    Best Regards,
    Radoslav Rusinov
    http://dba-blog.blogspot.com

  • Help.....help...me!!!

    Assignment A:
    Develop a banking system using object-oriented programming. The system will have a bank object, and customer objects.
    The details of the classes and their operations are as shown below:
    Classes Required:
    1. Class Bank (startup class)
    2. Class Customer
    3. Class FixCustomer and Class SavingCustomer
    Details of each class:
    Class Bank:
    Attributes - Information about the customer:
         a. Total number of customers registered (i.e. use an array to hold an array of customer objects)
    Behaviour - Bank's operations:
         a. Show Customer's balance
         b. Calculate & show Customer's interest
         c. Update customer's balance (e.g. after withdraw or deposit)
    This is the startup class. Create an interface that allows a potential customer to register. Also, an interface for registered user to access his/her account.
    Class Customer:
    Attributes - Information about a customer:
         a. Customer Name
         b. Customer Account number
         c. Customer Address
         d. Customer Phone Number
         e. Customer Job
         f. Customer Balance
    Behaviour - Customer's actions:
         a. Check account information (e.g. Balance )
         b. Withdraw
         c. Deposit
         d. Transfer (i.e. transferring credits from one user account to another)
    *Interest value for saving-account (Interest 5%), and fix-account (Interest 7%). These different interest values are declared in the SavingCustomer and FixCustomer classes.
    Assignment B:
    Draw the design of your system in UML diagrams - Class and state diagrams
    Explain and discuss about the design and implementation. You are also required to use flow-charts to document your codings.
    The deliverable:
    A report consisting of 10 to 20 pages. In the report, you must include:
         1.     Your UML diagrams. Class and state diagrams
         2.     Your program codes. (submit your codes in softcopy as well, in a disk)
         3.     Screen capture of all your user-interfaces.
         4.     Documentation from assignment B
         5.     Dateline: week 9

    What is the question?Hehe, i think the question is: "What's the code?"

  • Function LIMIT

    I have the following data in savings plan
    4051 wagetype (regular contribution) 10000 priority is set to L
    4054 wagetype catch up contribution  5000
    When i run payroll , at Function LIMIT
    Input is 4051 10000
    4054 : 5000
    processing
    Individual limits
    WT class      Interval           Origin              Reduction           Limit   Min
    401K          Y                 15,000.00           2,760.00          12,240.00   X
    401K          Y                 82,080.81           2,760.00          79,320.81
    Reduction amounts for IT
    WType                          Reduced by
    4051   B 05                  2,760.00
    2760 is already deducted in earlier pay periods
    Please help me understand this function LIMIT. I want 10000 to be deducted for wagetype 4051 , why it is not doing it. Why 2760 is going to DDNTK Table..
    Only 10000-2760=7240 is taken in this pay period.
    What should be done to fix it. Please advice
    Edited by: sagarika sharma on Aug 26, 2010 3:38 AM

    It is simple 401K Deduction wagetype 4051 and 401K catch wagetype are defined in the same wagetype class.Check table  V_T51D1.
    So already you have deducted 2,760.00  and now you are deduction 5000 from catch up, that comes to 7760 and out of 10,000 - only 7240  will be deducted as the total limit is set as 15,000.
    If you want to set 401K limit is 15,000 and 401K catch is 5,000 (If I'm right for 2010 401K limit 16,500 and catch up 5500). Then you have define two separate wagetype class say 41KR  and 41KC. Set the limit as 15,000 and 5,000. Assign wagetype  4051  to 41KR  (Regular)
    and 4054 wagetype to 41KC
    hope this helps. Please provide feedback- whether this solved your problem or not.

  • SAP HR implementation  ( MOST MOST URGENT )

    Hi Friends ,
    Just i wanted to know the following answers ?please kindly send me full - detail script .
    1. Project planning
    2. Documentation of Functional Specifications and communication to ABAP Programmers
    2. Blueprints (requirement analysis and process design)
    3. Realization (configuration, QA testing and production support hand-over)
    4. Go-live (data conversion, production system build and final QA testing)
    5. Production Support.
    Thanks and i appreciate your time .
    Regards- Zubair ( Australia )

    Business Blueprint
    Once a company decides to buy SAP, a consulting company is being hired for the implementation. The consulting company analyze the business process of the company and prepare a blueprint.
    Sometimes the business process is reengineered (BPR) to accommodate SAP's functionalities.
    The second step is installation of SAP and setting up three clients namely development client, test client and production clients.
    In the development client the SAP functional and development group start configuring the SAP based on the blueprint. Once it is completely configured, it is being transported to test client for testing using real time data. Once testing is successful, the configuration is being transported to production client to be used by real-time users.
    So this process makes SAP more reliable and robust in production.
    Preparation Before Implementing SAP
    SAP R/3 implementation is generally a key project for any organization. It is necessary to do preparation before implementation.
    Many organizations speak of "transferring technology." But what does that mean? Transfer technology involves transfer of the system which includes the
    hardware
    software
    people
    processes
    information
    organization
    structure
    synchronization
    function and
    behavior.
    It becomes obvious that the transfer of any part of the system, without the rest of it, does not transfer technology. In our context, the software SAP/3 is being changed. In most of the cases the hardware needs to be changed. The people need training to operate SAP system. But unfortunately, many organizations fail to understand that they need to change their processes. SAP is a package & it contains many best practices suitable to almost each industry. The designer (configuring the system) must design the system keeping the objective of the business objective in mind. The user should be prepared to change it’s processes and ensure that the objective of the processes is met. This should be done without or minimum distortion of the processes designed by SAP. This is a big challenge to the designer as well as user. It should noted that the user representative involved in the system design should be empowered for low level BPR decisions.
    Also the information stored in the system will be in different form than the legacy system. The user must be prepared & trained for the changed.
    The major challenge is behavioral change. Implementation of SAP R/3 system changes relationship of different persons, it gives/denies access to information which was not available/available to the person, it changes processes and control functions. This all gives behavioral issues. To get best out of SAP, these issues must be addressed before implementation.
    SAP R/3 re-engineers many processes and the fear of downsizing and loosing job hinders free acceptance of SAP in many organizations. This fear hinders free communication between the end-users and SAP system designer. The communication is a vital element in successful implementation of SAP R/3. This issue of 'Fear Of Downsizing' must be addressed before starting implementation project.
    ASAP Implementation Methodology
    Any enterprise application software has to cover a broad spectrum of functionality, yet to be configured enough to meet specific requirements. SAP achieves this by ASAP methodology & R/3 Business Engineer.
    AcceleratedSAP (ASAP) is SAP’s standard implementation methodology. It contains the Roadmap, a step-by step guide that incorporates experience from many years of implementing SAP. Quality checks are incorporated at end of each phase to ensure quality of deliverables and monitor critical success factors.
    ASAP is delivered as a PC based package, so that an implementation project can begin prior to having an SAP R/3 system installed
    ASAP Tools
    ASAP Roadmap
    ASAP and Business Engineer have compatibility with many third party modeling tools and packages like MS Excel etc
    Creating the Business Blueprint for Implementation Projects
    Purpose
    To create a Business Blueprint during the implementation of mySAP.com solution to document the business processes in an enterprise, and to decide which processes should realize in SAP system.
    The use of Business Blueprint in the Solution Manager during the realization phase (configuration and testing) should continue. It needs to reuse the project structure created in the Business Blueprint phase, to configure and generate test plans. One can also display, change and enhance project documentation created during the Business Blueprint phase, during configuration.
    Prerequisites
    You want to implement a mySAP.com solution. You have completed the Project Preparation: you have defined an implementation project and a system landscape in the project administration of the SAP Solution Manager.
    Process Flow
    ...Create a Blueprint structure, using predefined substructures.
    Check the Business Blueprint structure, and the business scenarios, business processes and process steps it contains.
    Decide which business scenarios, business processes and process steps you want to include in the Business Blueprint. You can enhance the processes and process steps, or adjust the names of individual processes to suit your company requirements.
    Create the project documentation and save it in the Business Blueprint.
    Assign transactions to process steps. This specifies which transactions in the system correspond to the process steps in your enterprise.
    Print the Business Blueprint document.
    When the Business Blueprint is complete, you can start to set up the development system landscape.
    Result
    You have created your Business Blueprint and set up your development system landscape. You can reuse the Business Blueprint and the project structure to configure and test your business processes
    Business Blueprint
    Use
    This function documents the business processes in your company that you want to implement in the system. In a Business Blueprint for Projects, you create a project structure in which relevant business scenarios, business processes and process steps are organized in a hierarchical structure. You can also create project documentation and assign it to individual scenarios, processes or process steps. You then assign transactions to each process step, to specify how your business processes should run in your SAP Systems.
    The Business Blueprint is a detailed description of your business processes and system requirements. You can print it out.
    Integration
    You can continue to use the project documentation and the project structure that you create during the Business Blueprint, in the configuration and test organization phases.
    • When you configure your business processes, the system displays the Business Blueprint project structure. You can use the Business Blueprint project structure as a point of reference during configuration.
    • You can also display and edit the project documentation from the Business Blueprint phase, during configuration.
    • You base all test plans that you create during test organization, on the Business Blueprint project structure. The transactions that you assign to process steps in the Business Blueprint are put in test plans during test plan generation, and run as function tests to test the transactions.
    Prerequisites
    You have created a project of type implementation, template, or upgrade, in the project administration.
    Features
    Scope of the transaction Business Bueprint
    Function Tab
    Create a project structure Structure
    Display the following documentation:
    • Documentation delivered by SAP, e.g. scenario descriptions
    • Documentats from templates, e.g. from template projects
    To be able to edit general documentation, copy it to the Project Documentation tab. General Documentation
    Assign documents to structure elements
    Create, Change, Upload user documents Project Documentation
    Input administration data, e.g. project status, team members assigned, planned and actual resources Administration
    Assign transactions and programs to structure elements Transactions
    Create, Display and Edit messages Messages
    Display and Create a process graphic
    Create a process graphic Graphic
    Where-used list:
    • Use in user project
    • Use in other projects
    • Go to use by double-click • General Documentation
    • Project Documentation
    • Transactions
    General Functions
    Function Navigation
    Change the sequence, hide or show tabs Settings ® User-Specific
    Translate project structure
    For further information about translating document names for URLs, in your project, see Translating a Template
    Goto &#61614; Translation
    Create/print a Business Blueprint document Business Blueprint &#61614; Create Blueprint Document
    Assign Document Authorizations
    Assign authorizations in the Role (PFCG) and User Maintenance.
    Activities
    1. Create a Blueprint structure in the Structure tab, using predefined substructures.
    2. Check the Business Blueprint structure, and the business scenarios, business processes and process steps it contains.
    3. Decide which business scenarios, business processes and process steps you want to include in the Business Blueprint. You can enhance the processes and process steps, or adjust the names of individual processes to suit your company requirements.
    4. Create project documentation to save in the Business Blueprint, in the Project Documentation tab.
    5. Assign transactions to process steps in the Transactions tab. This specifies which transactions in the system correspond to the process steps in your enterprise.
    6. Print the Business Blueprint document.
    7. When the Business Blueprint is complete, you can start to set up the development system landscape.
    Result
    You have specified a Business Blueprint. You can reuse the Business Blueprint and the project structure to configure and test your business processes.
    Business Blueprint
    Definition
    A Business Blueprint documents the business process requirements of a company. In collaborative business processes, several companies are involved.
    Use
    The Business Blueprint gives you a general idea of how your business processes could be mapped in one or more SAP Systems. The Business Blueprint documents in detail the scope of business scenarios, business processes, process steps, and the requirements of a mySAP.com solution implementation.
    Structure
    A Business Blueprint compises the following structure elements in a hierarchy:
    • Organizational units
    • Master data
    • Business scenarios
    • Business processes
    • Process steps
    You assign content, for example, project documentation, Business Configuration Sets, or transactions to individual structure elements, in the SAP Solution Manager.
    You can also create structure elements for organizational units and master data, below a business scenario. You only use these structure elements if the organizational units and master data are only relevant to the business process above them in the structure.
    09885707073

Maybe you are looking for