FM in std rule

Dear Experts,
In std rule 00000168 to find Superior of an employee FM SWX_GET_MANAGER is used. In that FM code for getting is given as below.
SWC_GET_ELEMENT AC_CONTAINER 'OTYPE' ORG_TYPE.
  SWC_GET_ELEMENT AC_CONTAINER 'OBJID' ORG_ID.
When I simulate the rule in PFAC I get the output. From SE37 I populate AC_CONTAINER with values that I gave in PFAC as below.
ELEMENT - OTYPE   VALUE  -  US
ELEMENT - OBJID     VALUE -  ABAPER
But I see that these values are not set for ORG_TYPE AND ORG_ID. Can you please tell me how to pass values correctly to this FM. I have employee OTYPE & OBJID as input. I need to find the Superior of this employee.
KR,
Bharath

Dear All,
Thanks a lot for all your inputs.
I have solved the problem. FM RH_GET_ACTORS is used to call any rule. Find the code of my solution below.
FUNCTION ZGETMGR.
*"*"Local Interface:
*"  TABLES
*"      ACTOR_TAB STRUCTURE  SWHACTOR
  INCLUDE <cntn01>.
  DATA: lt_agents type standard table of swhactor.
  swc_container lt_container.
  swc_set_element lt_container 'OTYPE' 'US'.
  swc_set_element lt_container 'OBJID' 'ABAPER'.
  CALL FUNCTION 'RH_GET_ACTORS'
    EXPORTING
      ACT_OBJECT                = 'AC00000168'
    TABLES
      ACTOR_CONTAINER           = lt_container
      ACTOR_TAB                 = lt_agents
    EXCEPTIONS
      NO_ACTIVE_PLVAR           = 01
      NO_ACTOR_FOUND            = 02
      EXCEPTION_OF_ROLE_RAISED  = 03
      NO_VALID_AGENT_DETERMINED = 04
      NO_CONTAINER              = 05
      OTHERS                    = 06.
  actor_tab[] = lt_agents[].
ENDFUNCTION.
In above FM ACTOR_CONTAINER is the input where we give the employee for whom we want to find the supervisor and
ACTOR_TAB is the output which contains the OTYPE & OBJID of Supervisor. ACT_OBJECT is the name of the rule.
KR,
Bharath

Similar Messages

  • How to create new rules for agent assignment

    Hi all,
    I have a situation in which the esclation has to occur to the second line manager . is there any rule avail. for agent assignemnt and if not how I can creaet a new rule
    Thanks in advance..

    Hi,
    One way is you can call SWX_GET_MANAGER function module twice for getting your manager's manger.
    For creating new rule, you can copy any std rule and themn modify the copied rule using txn PFAC. e.g check out rule - 00000168, which uses above mentioned FM - SWX_GET_MANAGER .
    Hope this helps.
    Regds,
    Akshay

  • Date Rules failing in billing value

    Hi All,
    I have created a date rule with the help of an existing date std rule.
    I need the rule as monthly (considering month as 30 days).
    <?xml version="1.0"?>
    <SAPTimeRule>
       <TimeRuleTree>
       <!-- Begin of Rule Tree -->
          <ruleline>
          <!-- Begin of new LINE -->
             <AssignTimeExp displaytype="AssignTime">
             <!-- Assign time -->
                <VarTimeExp displayType="VarTime"
                                   name="RESULT"
                               position="B">
                <!-- Variable: Time -->
                </VarTimeExp>
                <MoveTimeExp displaytype="MoveTime" direction="+">
                <!-- Move -->
                   <VarTimeExp displayType="VarTime"
                                      name="PERIOD_DATE"
                                      position="B">
                   <!-- Variable: Time -->
                   </VarTimeExp>
                   <ConstDuraExp displaytype="ConstDura"
                                    duration="1" timeunit="MONTH">
                   <!-- Constant Duration -->
                      <VarObjectExp displaytype="VarObject"
                                    name="SYSTEM"/>
                      <!-- Variable: Timeobject -->
                   </ConstDuraExp>
                </MoveTimeExp>
             </AssignTimeExp>
          </ruleline>
       </TimeRuleTree>
    </SAPTimeRule>
    When I specified it as
                  <ConstDuraExp displaytype="ConstDura"
                                    duration="1" timeunit="MONTH">
    Its working fine and gives the billing value properly.
    When I specify it as
                  <ConstDuraExp displaytype="ConstDura"
                                    duration="30" timeunit="DAY">
    Its not showing consistant billing value for all the period.
    Do I need to do anything with date profile or duration.
    Can anybody help me to proceed?
    Thanks & Regards,
    bhuvana

    Hi Martin,
    I will explain my problem again.
    I have created a date rule with the help of an existing date std rule.
    I need the rule as monthly (considering month as 30 days).
    <?xml version="1.0"?>
    <SAPTimeRule>
    <TimeRuleTree>
    <!-- Begin of Rule Tree -->
    <ruleline>
    <!-- Begin of new LINE -->
    <AssignTimeExp displaytype="AssignTime">
    <!-- Assign time -->
    <VarTimeExp displayType="VarTime"
    name="RESULT"
    position="B">
    <!-- Variable: Time -->
    </VarTimeExp>
    <MoveTimeExp displaytype="MoveTime" direction="+">
    <!-- Move -->
    <VarTimeExp displayType="VarTime"
    name="PERIOD_DATE"
    position="B">
    <!-- Variable: Time -->
    </VarTimeExp>
    <ConstDuraExp displaytype="ConstDura"
    duration="1" timeunit="MONTH">
    <!-- Constant Duration -->
    <VarObjectExp displaytype="VarObject"
    name="SYSTEM"/>
    <!-- Variable: Timeobject -->
    </ConstDuraExp>
    </MoveTimeExp>
    </AssignTimeExp>
    </ruleline>
    </TimeRuleTree>
    </SAPTimeRule>
    When I specified it as
    <ConstDuraExp displaytype="ConstDura"
    duration="1" timeunit="MONTH">
    Its working fine and gives the billing value properly as below.
    from                              to                           bill date                  <b>bill value</b>
    05.11.2007     04.12.2007     01.11.2007     0.83
    05.12.2007     04.01.2008     01.12.2007     0.83
    05.01.2008     04.02.2008     01.01.2008     0.83
    05.02.2008     04.03.2008     01.02.2008     0.83
    05.03.2008     04.04.2008     01.03.2008     0.83
    05.04.2008     04.05.2008     01.04.2008     0.83
    05.05.2008     04.06.2008     01.05.2008     0.83
    05.06.2008     04.07.2008     01.06.2008     0.83
    05.07.2008     04.08.2008     01.07.2008     0.83
    05.08.2008     04.09.2008     01.08.2008     0.83
    05.09.2008     04.10.2008     01.09.2008     0.83
    05.10.2008     04.11.2008     01.10.2008     0.00
    When I specify it as
    <ConstDuraExp displaytype="ConstDura"
    duration="30" timeunit="DAY">
    Its not showing consistant billing value for all the period.
    from                               to                         bill date                    bill value
    05.11.2007     04.12.2007     01.11.2007     100.83
    05.12.2007     03.01.2008     01.12.2007     0.69
    04.01.2008     02.02.2008     01.01.2008     0.69
    03.02.2008     03.03.2008     01.02.2008     0.83
    04.03.2008     02.04.2008     01.03.2008     0.69
    03.04.2008     02.05.2008     01.04.2008     100.83
    03.05.2008     01.06.2008     01.05.2008     0.69
    02.06.2008     01.07.2008     01.06.2008     100.83
    02.07.2008     31.07.2008     01.07.2008     0.69
    01.08.2008     30.08.2008     01.08.2008     100.83
    31.08.2008     29.09.2008     01.08.2008     0.69
    30.09.2008     29.10.2008     01.09.2008     100.83
    30.10.2008     04.11.2008     01.10.2008     0.00
    But te period is getting splitted correctly for 30 days.
    What could be the problem?
    Can you guid to correct this problem?
    Thanks & Regards,
    Bhuvana

  • 4 Entries for 1 purchase of capital goods

    Dear Gurus,
    I am Purchasing excisable Capital Goods ( Either from local or Import Vendor). In both cases in RG 23 c Part 1, register shows 4 entries for only one capital purchase. BUt in RG23part2, system is considering first entry out of 4 entries from RG23CPart 1.WHy it is like that ?.
    What is the CIN Rule for AED. is is 50 % this year  and 50% next year or full 100 % in current year in case of capital goods AED.
    Please Help.
    Thanx in advance.

    As per Std. rule u can take the ADC credit 100% in the Current year for Capital Goods.
    Biswajit

  • PO requisition workflow error.

    Hi all,
    I am getting an error while the approval for the PO requisition.
    Error - "the user exceeds the limit" .
    Is it because i have maintained the user as both technical and non-technical approver?.
    I have checked in the function module for approvers also.
    Please suggest if anybody come across this kind of error.
    Regards,
    Neslin.

    Hi Neslin,
    are you using PO or PR,
    PO its BUS2012,
    PR (overall) its BUS2105
    PR (item) its BUS2009,
    now since u said, u are using a FM, where are u using it,
    are u using any rule.
    if u using a rule, and say u using BUS2105 in ur WF, just check the rule, it might have containers referring BUS2009, because of which the error might occur.
    and in some std.rules there might be containers like ReleaseCode which is mandatory,
    so while executing ur WF if it doesnt get a Release Code, it would fire an error.
    Pls check all of them.
    Aditya

  • What are the ways to make Query run fast?

    Hi Experts,
    When a query runs slow, we generally go for creating an aggregate. My doubt is - what other things can be done to make a query run faster before creating an aggregate? What is the thumb rule to be carried out for creating an aggregate?
    Regards,
    Shreeem

    Hi Shreem,
    If you keep Query simple not complicate it with runtime calculations , it would be smooth. However as per business requirements we will have to go for it anyways mostly.
    regarding aggregates:
    Please do not use the standard proposal , it will give you hundreds based on std. rules , which consumes lots of space and adds up to load times. If you have users already using the Query and you are planning to tune it  then go for the statistics tables:
    1.RSDDSTAT_OLAP    find the query with long runtimes  get the Stepuid
    2. RSDDSTAT_DM
    3. RSDDSTATAGGRDEF  - use the stepuid above to see which aggregate is necessary for which cube.
    Another way to check ; check the users as in 1 to find the highest runtime users and find the last used bookmarks by user thru RSZWBOOKMARK for this query and check if the time matches and create the aggregates as in 3 above.
    You can also Use Transaction RSRT > execute & debug  (display stats ) - to create generic aggregates to support navigations for New queries and later refine as above.
    Hope it helps .
    Thnks
    Ram

  • When index's need to be deleted in process chain

    Hi Friends ,
       I am looking for some info in what scenarios the indexes need to be deleted & recreated  when loading data into a infocube thru process chain.
        I am looking for hard figures\ std rules like at  what % of new data  indexs can be dropped etc .., 
       Thanks

    Hi Sri:
    There is no formula. You need to do a small experiment with your Cube to determin this criterion. This is because the loading data to Cube not only depends on the number of records, bit other factors such as new SIDs, etc.
    I would manually load the Cube with the number of recrods equal to the usual number.
    Take the time.
    Now, delete and create indexes in Batch Job in BW for the Cube. Again, note the total time.
    If the second time is significant, dont't delete indexes, let BW manage them.
    In my case, I load 2 cubes daily with same infopackage.
    1 - deleted and laoded.
    2 - history with deifferent level of aggregation.
    No. of records  = 1 mil.
    Cube 1 - I delete indexes and create them.
    Cube 2 - Don't delete this because this cubes keeps growing bigger and deleting and creating indexes will give diminishing returns.
    FOr these bix Cubes, I do a seperate P-Chain to drop and create indexes on Sundays when no users are querying the Cubes.
    Hope this will explain, but I don't have a formula.
    Ram Chamarthy.

  • How to link organizational unit to org. Object type ?

    Hello,
    i want to link an organizational unit to the object type T024L, Does anyone know how i can do this ?
    Thanks a lot

    Hi,
    You need to create assignment between Org object type and org unit. Use txn <b>PFOM - Create Assignments</b> for the same.
    You can then try the std rule 30100012 also.
    Hope this helps.
    Regds,
    Akshay Bhagwat
    PS: Some points would be nice if it helps

  • Subcontracting (180)

    hello Guru
    Insubcontracting Scenario. when send materail for some work
    but as per std rule he(subcontracter may send material whithin 180days
    if he is unable to send within 180 days how u going to make scenario
    if u may scrapp it or make excise in voice  plz explain me the scenario in detail
    Regards
    sapman

    Hi,
           The material must have been issued to Sub-contractor via 541 transaction.
    Use 542 transcation in MB1B for bringing back the goods to inventory stock . Now
    you can close the old excise papers & reissue the materials via 541 transaction &
    now make new exceise papers . Hope this solves your problem.
    regards
    Bijoy

  • Payroll should pick no of hours worked from attendence infotype

    Hi ,
    I got one requirement. When we are running pay roll no of hours worked is picked from workschedule.But my requirement is it should pick up from attendence infotype . Can anyone tell me the rule name that attendence will be picked up.
    Please throw some light on this issue.
    Thanks and Regards
    Visali.Malepati.

    Hi Manu,
    Instead of creating a customized rule directly first  I want to know is there any SAP std rule  to do this.
    Please kindly help.
    Thanks and Regards,
    Visali.Malepati.

  • Arrear Break-up

    My client requires component0wise Break-up for
    Basic ( Real,Arrears,Retro)
    HRA breaku[ as above
    FBP as above
    I'm getting /551 and /552 but that's not sufficing the Purpose
    Pl explain what to be done where
    Thanks in advance
    BHarat

    Hi
    Did you created all the wagetypes you mentioned up.
    If you did then you have to check the difference table and make arrangements in the rule as it always done you can take help from the std rule.
    If anything else reply.

  • DOGBOY49  This is for you

    I saw in one of your posts that you are able to upload routing successfully through direct input methode.
    I am trying to upload routing through Batch input methode but it is not picking my operation information.
    When it goes to this screen it says no relevent information is provided for this screen.
    Can you provide me your structure relation ship and field mapping information.
    Regards
    Deepu P.
    Edited by: deepu p on Jan 23, 2009 12:12 AM

    Deepu,
    Program is RCPTRA02.  It is probably possible to do this more than
    one way, but this is the way we do it, in part because of the structure
    of the data that our manufacturing group is able to give to us.
    We never use teardown, we generally ONLY use setup time for fixed time
    operations,  We don't have multiple sequences. We use one routing for
    all lot sizes.
    First I do an inital pass, as follows.  Creates the header and one fixed time
    operation. Machine time is blank in the input file for fixed time ops.  First
    pass, PLNNR will be blank. Name of the file is ROUTING.CSV and
    Structure is ROUTING
    Input file fields
    WERKS                          C(004)    plant
    KTEXT                          C(040)    Name
    ARBPL                          C(008)    work center
    VORNR                          C(004)    Operation Number
    PLNNR                          C(008)    Routing Group
    LTXA1                          C(030)    Operation Name
    BMSCH                          N(010)    Base Quantity
    VGW01                          N(010)    Setup Time Std
    VGE01                          C(003)    Setup Time Unit
    VGW02                          N(010)    Machine Time Std
    VGE02                          C(003)    Machine Time Unit
    Field Mapping
    SFC - ROUTING Create Routing (inital data plus admin Operation)
        RC271_DS                       Work center structure for direct input (for datasets)
          Fields
              TCODE                        Transaction code
                                  Rule :   Constant
                                  Coding:  RC271_DS-TCODE = 'CA01'.
              STTAG                        Character field length = 10
                                  Coding:  RC271_DS-STTAG = '01/01/2006'.
              AENNR                        Change number
              REVLV                        Revision level
              WERKS                        Plant
              PROFIDNETZ                   Profile
              PLNNR                        Key for task list group
              PLNAL                        Group counter
                                  Rule :   Constant
                                  Coding:  RC271_DS-PLNAL = '01'.
              STATU                        Status
              VAGRP                        Responsible planner group/department
              VBELN                        Sales document
              POSNR                        Character field of length 6
              PSPNR                        Work Breakdown Structure Element (WBS Element)
          PLKO_DI_DS                     Header structure for direct input (for datasets)
              Fields
                  ACTTYP                       Processing type for objects to be imported
                                      Rule :   Constant
                                      Coding:  PLKO_DI_DS-ACTTYP = 'H'.
                  PLNAL                        Group counter
                                      Rule :   Constant
                                      Coding:  PLKO_DI_DS-PLNAL = '01'.
                  VERWE                        Use by user or system
                                      Rule :   Constant
                                      Coding:  PLKO_DI_DS-VERWE = '1'.
                  WERKS                        Plant
                                      Source:  ROUTING-WERKS (plant)
                                      Rule :   Transfer (MOVE)
                                      Coding:  PLKO_DI_DS-WERKS = ROUTING-WERKS.
                  STATU                        Status
                                      Rule :   Constant
                                      Coding:  PLKO_DI_DS-STATU = '4'.
                 PLNME                        Unit of measure for the task list (batch input)
                                     Rule :   Constant
                                     Coding:  PLKO_DI_DS-PLNME = 'EA'.
                 LOSVN                        From lot size (BTCI)
                 LOSBS                        To lot size (BTCI)
                                     Rule :   Constant
                                     Coding:  PLKO_DI_DS-LOSBS = '99999999'.
                 VAGRP                        Responsible planner group/department
                                     Rule :   Constant
                                     Coding:  PLKO_DI_DS-VAGRP = '001'.
                 KTEXT                        Task list description
                                     Source:  ROUTING-KTEXT (Name)
                                     Rule :   Transfer (MOVE)
                                     Coding:  PLKO_DI_DS-KTEXT = ROUTING-KTEXT.
                 TXTSP                        Single-character flag
                 QDYNREGEL                    Dynamic Modification Rule
                 QDYNHEAD                     Level at Which Dynamic Modification Parameters Are Defined
         PLPO_DI_DS                     Routing/item structure for direct input (for datasets)
             Fields
                 ACTTYP                       Processing type for objects to be imported
                                     Rule :   Constant
                                     Coding:  PLPO_DI_DS-ACTTYP = 'H'.
                 PLNAL                        Group counter
                                     Rule :   Constant
                                     Coding:  PLPO_DI_DS-PLNAL = '01'.
                 PLNFL                        Sequence
                                     Rule :   Constant
                                     Coding:  PLPO_DI_DS-PLNFL = '000000'.
                 VORKN                        Node number (batch input)
                 VORNR                        Operation Number
                                     Source:  ROUTING-VORNR (Operation Number)
                                     Rule :   Transfer (MOVE)
                                     Coding:  PLPO_DI_DS-VORNR = ROUTING-VORNR.
    Attention: Source field is longer than target field!
                 UVOKN                        Node number (batch input)
                 UVORN                        Sub-operation
                 STEUS                        Control key
                                                     Rule :   Constant
                                     Coding:  PLPO_DI_DS-STEUS = '0009'.
                 ARBID                        Object ID (batch input)
                 OBJTY                        Object types of the CIM resource
                 ARBPL                        Work center
                                     Source:  ROUTING-ARBPL (work center)
                                     Rule :   Transfer (MOVE)
                                     Coding:  PLPO_DI_DS-ARBPL = ROUTING-ARBPL.
                 WERKS                        Plant
                                     Source:  ROUTING-WERKS (plant)
                                     Rule :   Transfer (MOVE)
                                     Coding:  PLPO_DI_DS-WERKS = ROUTING-WERKS.
                 KTSCH                        Standard text key
                 LTXA1                        Short text
                                     Source:  ROUTING-LTXA1 (Operation Name)
                                     Rule :   Transfer (MOVE)
                                     Coding:  PLPO_DI_DS-LTXA1 = ROUTING-LTXA1.
                 VPLTY                        Type of the referenced task list
                 VPLNR                        Group of the referenced task list
                 VPLAL                        Group counter of the referenced task list
                 VPLFL                        Referenced sequence in routing
                 VINTV                        Operation interval
                 MEINH                        Quantity unit for operation (batch input)
                                     Rule :   Constant
                                     Coding:  PLPO_DI_DS-MEINH = 'EA'.
                 UMREN                        Denominator for conversion from unit to base unit (BTCI)
                                     Rule :   Constant
                                     Coding:  PLPO_DI_DS-UMREN = '1'.
                 UMREZ                        Numerator for converting from unit to base unit (BTCI)
                                     Rule :   Constant
                                     Coding:  PLPO_DI_DS-UMREZ = '1'.
                 BMSCH                        Base quantity (Batch input)
                                     Source:  ROUTING-BMSCH (Base Quantity)
                                     Rule :   Transfer (MOVE)
                                     Coding:  PLPO_DI_DS-BMSCH = ROUTING-BMSCH.
                 ZMERH                        Break time (batch input)
                 ZEIER                        Unit for break time (batch input)
                 LAR01                        Activity Type 
                  ZEIER                        Unit for break time (batch input)
                  LAR01                        Activity Type
                  VGE01                        Unit for the standard value (batch input)
                                      Source:  ROUTING-VGE01 (Setup Time Unit)
                                      Rule :   Transfer (MOVE)
                                      Coding:  PLPO_DI_DS-VGE01 = ROUTING-VGE01.
    Attention: Source field is longer than target field!
                  VGW01                        Standard value (batch input)
                                      Source:  ROUTING-VGW01 (Setup Time Std)
                                      Rule :   Transfer (MOVE)
                                      Coding:  PLPO_DI_DS-VGW01 = ROUTING-VGW01.
                  LAR02                        Activity Type
                  VGE02                        Unit for the standard value (batch input)
                                      Source:  ROUTING-VGE02 (Machine Time Unit)
                                      Rule :   Transfer (MOVE)
                                      Coding:  PLPO_DI_DS-VGE02 = ROUTING-VGE02.
                  VGW02                        Standard value (batch input)
                                      Source:  ROUTING-VGW02 (Machine Time Std)
                                      Rule :   Transfer (MOVE)
                                      Coding:  PLPO_DI_DS-VGW02 = ROUTING-VGW02.
                  LAR03                        Activity Type
    Remaining fields unmapped.
    The first operation in our routings is always '0010' and is always a non-capacity consuming op (fixed time).  Our Control key is always 0009.
    Next, we add cap-consuming ops, one at a time, using another LSMW.  So,
    all operation 0020 one pass; all routings.  all operation 0030, one pass, all routings;
    etc etc.
    Input file fields same as above, except in this case we generally leave the setup time blank and
    instead enter the machine time.  Name of the file is ROUTING1.CSV and structure is ROUTING1.
    YOU HAVE TO HAVE THE ROUTING NUMBER GENERATED IN THE FIRST LSMW RUN and
    insert it into PLNNR.
    Mapping:
    - SFC - ROUTING1 Change Routing (add cap based WCs)
    Fielddmapping and conversion rules
       RC271_DS                       Work center structure for direct input (for datasets)
           Fields
               TCODE                        Transaction code
                                   Coding:  RC271_DS-TCODE = 'CA02'.
               STTAG                        Character field length = 10
                                   Coding:  RC271_DS-STTAG = '01/01/2006'.
               AENNR                        Change number
               REVLV                        Revision level
               WERKS                        Plant
               PROFIDNETZ                   Profile
               PLNNR                        Key for task list group
                                   Source:  ROUTING1-PLNNR (Routing Group)
                                   Rule :   Transfer (MOVE)
                                   Coding:  RC271_DS-PLNNR = ROUTING1-PLNNR.
               PLNAL                        Group counter
                                   Rule :   Constant
                                   Coding:  RC271_DS-PLNAL = '01'.
               STATU                        Status
               VAGRP                        Responsible planner group/department
               VBELN                        Sales document
               POSNR                        Character field of length 6
               PSPNR                        Work Breakdown Structure Element (WBS Element)
           PLPO_DI_DS                     Routing/item structure for direct input (for datasets)
               Fields
                   ACTTYP                       Processing type for objects to be imported
                                       Rule :   Constant
                                       Coding:  PLPO_DI_DS-ACTTYP = 'H'.
                   PLNAL                        Group counter
                                       Rule :   Constant
                                       Coding:  PLPO_DI_DS-PLNAL = '01'.
                   PLNFL                        Sequence
                                       Rule :   Constant
                                       Coding:  PLPO_DI_DS-PLNFL = '000000'.
                   VORKN                        Node number (batch input)
                    VORNR                        Operation Number
                                           Source:  ROUTING1-VORNR (Operation Number)
                                           Rule :   Transfer (MOVE)
                                           Coding:  PLPO_DI_DS-VORNR = ROUTING1-VORNR.
    Attention: Source field is longer than target field!
                       UVOKN                        Node number (batch input)
                       UVORN                        Sub-operation
                       STEUS                        Control key
                                           Rule :   Constant
                                           Coding:  PLPO_DI_DS-STEUS = '0009'.
                       ARBID                        Object ID (batch input)
                       OBJTY                        Object types of the CIM resource
                       ARBPL                        Work center
                                           Source:  ROUTING1-ARBPL (work center)
                                           Rule :   Transfer (MOVE)
                                           Coding:  PLPO_DI_DS-ARBPL = ROUTING1-ARBPL.
                       WERKS                        Plant
                                           Source:  ROUTING1-WERKS (plant)
                                           Rule :   Transfer (MOVE)
                                           Coding:  PLPO_DI_DS-WERKS = ROUTING1-WERKS.
                       KTSCH                        Standard text key
                       LTXA1                        Short text
                                           Source:  ROUTING1-LTXA1 (Operation Name)
                                           Rule :   Transfer (MOVE)
                                           Coding:  PLPO_DI_DS-LTXA1 = ROUTING1-LTXA1.
                       VPLTY                        Type of the referenced task list
                       VPLNR                        Group of the referenced task list
                       VPLAL                        Group counter of the referenced task list
                       VPLFL                        Referenced sequence in routing
                       VINTV                        Operation interval
                       MEINH                        Quantity unit for operation (batch input)
                                           Rule :   Constant
                                           Coding:  PLPO_DI_DS-MEINH = 'EA'.
                       UMREN                        Denominator for conversion from unit to base unit (BTCI)
                                           Rule :   Constant
                                           Coding:  PLPO_DI_DS-UMREN = '1'.
                       UMREZ                        Numerator for converting from unit to base unit (BTCI)
                                           Rule :   Constant
                                           Coding:  PLPO_DI_DS-UMREZ = '1'.
                      BMSCH                        Base quantity (Batch input)
                                          Source:  ROUTING1-BMSCH (Base Quantity)
                                          Rule :   Transfer (MOVE)
                                          Coding:  PLPO_DI_DS-BMSCH = ROUTING1-BMSCH.
                      ZMERH                        Break time (batch input)
                      ZEIER                        Unit for break time (batch input)
                      LAR01                        Activity Type
                      VGE01                        Unit for the standard value (batch input)
                                          Source:  ROUTING1-VGE01 (Setup Time Unit)
                                          Rule :   Transfer (MOVE)
                                          Coding:  PLPO_DI_DS-VGE01 = ROUTING1-VGE01.
    Attention: Source field is longer than target field!
                      VGW01                        Standard value (batch input)
                                          Source:  ROUTING1-VGW01 (Setup Time Std)
                                          Rule :   Transfer (MOVE)
                                          Coding:  PLPO_DI_DS-VGW01 = ROUTING1-VGW01.
                      LAR02                        Activity Type
                      VGE02                        Unit for the standard value (batch input)
                                          Source:  ROUTING1-VGE02 (Machine Time Unit)
                                          Rule :   Transfer (MOVE)
                                          Coding:  PLPO_DI_DS-VGE02 = ROUTING1-VGE02.
                      VGW02                        Standard value (batch input)
                                          Source:  ROUTING1-VGW02 (Machine Time Std)
                                          Rule :   Transfer (MOVE)
                                          Coding:  PLPO_DI_DS-VGW02 = ROUTING1-VGW02.
                      LAR03                        Activity Type
                      VGE03                        Unit for the standard value (batch input)
                      VGW03                        Standard value (batch input)
                      LAR04                        Activity Type
                      VGE04                        Unit for the standard value (batch input)
                      VGW04                        Standard value (batch input)
                      LAR05                        Activity Type
                      VGE05                        Unit for the standard value (batch input)
                      VGW05                        Standard value (batch input)
                      LAR06                        Activity Type
                      VGE06                        Unit for the standard value (batch input)
                      VGW06                        Standard value (batch input)
                      ZERMA                        Type of standard value calculation
                      ZGDAT                        Date when the standard value was calculated
                      ZCODE                        Reference number for standard value code
                      ZULNR                        Basis for standard value calculation
                      RSANZ                        Number of confirmation slips (batch input)
                      LOANZ                        Number of time tickets (batch input)
                      LOART                        Wage type
                      QUALF                        Suitability
                      ANZMA                        Number of employees (Batch-input)
                      RFGRP                        Setup group category
                      RFSCH                        Setup group key
                      RASCH                        Setup type key
                      AUFAK                        Scrap factor (batch input)
                      LOGRP                        Wage group
                      UEMUS                        Required overlapping
                      UEKAN                        Optional overlapping
                      FLIES                        Indicator: continuous flow production
                      ZEIMU                        Unit for minimum overlap time (batch input)
                      ZMINU                        Minimum overlap time (batch input)
                      MINWE                        Minimum send-ahead quantity (batch input)
                      SPMUS                        Required splitting
                                          Rule :   Constant
                                          Coding:  PLPO_DI_DS-SPMUS = 'X'.
    Remaining fields unmapped.
    Finally, we add the remaining fixed time operations.  Same input fields, name of structure is ROUTING2
    Field Mapping:
    Fieldmapping and conversion rules
       RC271_DS                       Work center structure for direct input (for datasets)
           Fields
               TCODE                        Transaction code
                                   Coding:  RC271_DS-TCODE = 'CA02'.
               STTAG                        Character field length = 10
                                   Coding:  RC271_DS-STTAG = '01/01/2006'.
               AENNR                        Change number
               REVLV                        Revision level
               WERKS                        Plant
               PROFIDNETZ                   Profile
               PLNNR                        Key for task list group
                                   Source:  ROUTING2-PLNNR (Routing Group)
                                   Rule :   Transfer (MOVE)
                                   Coding:  RC271_DS-PLNNR = ROUTING2-PLNNR.
               PLNAL                        Group counter
                                   Rule :   Constant
                                   Coding:  RC271_DS-PLNAL = '01'.
               STATU                        Status
               VAGRP                        Responsible planner group/department
               VBELN                        Sales document
               POSNR                        Character field of length 6
               PSPNR                        Work Breakdown Structure Element (WBS Element)
           PLPO_DI_DS                     Routing/item structure for direct input (for datasets)
               Fields
                   ACTTYP                       Processing type for objects to be imported
                                       Rule :   Constant
                                       Coding:  PLPO_DI_DS-ACTTYP = 'H'.
                   PLNAL                        Group counter
                                       Rule :   Constant
                                       Coding:  PLPO_DI_DS-PLNAL = '01'.
                   PLNFL                        Sequence
                                       Rule :   Constant
                                       Coding:  PLPO_DI_DS-PLNFL = '000000'.
                   VORKN                        Node number (batch input)
                   VORNR                        Operation Number
                                       Source:  ROUTING2-VORNR (Operation Number)
    Attention: Source field is longer than target field!
                  UVOKN                        Node number (batch input)
                  UVORN                        Sub-operation
                  STEUS                        Control key
                                      Rule :   Constant
                                      Coding:  PLPO_DI_DS-STEUS = '0009'.
                  ARBID                        Object ID (batch input)
                  OBJTY                        Object types of the CIM resource
                  ARBPL                        Work center
                                      Source:  ROUTING2-ARBPL (work center)
                                      Rule :   Transfer (MOVE)
                                      Coding:  PLPO_DI_DS-ARBPL = ROUTING2-ARBPL.
                  WERKS                        Plant
                                      Source:  ROUTING2-WERKS (plant)
                                      Rule :   Transfer (MOVE)
                                      Coding:  PLPO_DI_DS-WERKS = ROUTING2-WERKS.
                  KTSCH                        Standard text key
                  LTXA1                        Short text
                                      Source:  ROUTING2-LTXA1 (Operation Name)
                                      Rule :   Transfer (MOVE)
                                      Coding:  PLPO_DI_DS-LTXA1 = ROUTING2-LTXA1.
                  VPLTY                        Type of the referenced task list
                  VPLNR                        Group of the referenced task list
                  VPLAL                        Group counter of the referenced task list
                  VPLFL                        Referenced sequence in routing
                  VINTV                        Operation interval
                  MEINH                        Quantity unit for operation (batch input)
                                      Rule :   Constant
                                      Coding:  PLPO_DI_DS-MEINH = 'EA'.
                  UMREN                        Denominator for conversion from unit to base unit (BTCI)
                                      Rule :   Constant
                                      Coding:  PLPO_DI_DS-UMREN = '1'.
                  UMREZ                        Numerator for converting from unit to base unit (BTCI)
                                      Rule :   Constant
                                      Coding:  PLPO_DI_DS-UMREZ = '1'.
                    BMSCH                        Base quantity (Batch input)
                                       Source:  ROUTING2-BMSCH (Base Quantity)
                                       Rule :   Transfer (MOVE)
                                       Coding:  PLPO_DI_DS-BMSCH = ROUTING2-BMSCH.
                   ZMERH                        Break time (batch input)
                   ZEIER                        Unit for break time (batch input)
                   LAR01                        Activity Type
                   VGE01                        Unit for the standard value (batch input)
                                       Source:  ROUTING2-VGE01 (Setup Time Unit)
                                       Rule :   Transfer (MOVE)
                                       Coding:  PLPO_DI_DS-VGE01 = ROUTING2-VGE01.
    Attention: Source field is longer than target field!
                   VGW01                        Standard value (batch input)
                                       Source:  ROUTING2-VGW01 (Setup Time Std)
                                       Rule :   Transfer (MOVE)
                                       Coding:  PLPO_DI_DS-VGW01 = ROUTING2-VGW01.
                   LAR02                        Activity Type
                   VGE02                        Unit for the standard value (batch input)
                                       Source:  ROUTING2-VGE02 (Machine Time Unit)
                                       Rule :   Transfer (MOVE)
                                       Coding:  PLPO_DI_DS-VGE02 = ROUTING2-VGE02.
                   VGW02                        Standard value (batch input)
                                       Source:  ROUTING2-VGW02 (Machine Time Std)
                                       Rule :   Transfer (MOVE)
                                       Coding:  PLPO_DI_DS-VGW02 = ROUTING2-VGW02.
                   LAR03                        Activity Type
                   VGE03                        Unit for the standard value (batch input)
    Remaining fields unmapped.
    That's it.
    Regards,
    DB49

  • Email to Support Team fails !!!!

    Dear friends,
    i am having problems in sending an email to support team as soon as the support team is created..
    I am using std rule 13200137 and i have configured responsibilites, and this rule works fine and automatic support team is found out as soon as the support team is created ..
    But i have also created an action for sending an Email to support team as soon as the support team is  created.. which unfortunately is not triggered as soon as the msg is created but is triggered when the support msg is opened for changes...
    i have properly configured the action and its start condition and still the problem persists..
    I have also used email to msg creator(Sap Standard ) action which is getting triggered properly..
    Is it that i am having too many actions triggering at the creation of the support msg that is creating the problem.??
    plz help as ASAP...

    Suzzane,
    I have a quick question regards Email to Suppor Team. I understand that you have to maintain the email address in the ORG level for support Team email address. That looks like a group email address I have to assign to it. Can I make to send to employee(Solver) email addresses instead of creating a group email address and adding those employee email address to group. Please adivce on this.
    Thanks
    Kumar

  • Spamassassin Trustpath - trusted_networks

    Following this being brought up in another question, I had a closer look at the subject. I previously set trusted_networks to just local LAN (where server is NATed) but I found a couple of things I had not really noticed before and thought I would start another thread to ensure my new understanding is correct...
    Basic link on Trustpath...
    http://wiki.apache.org/spamassassin/TrustPath
    Of particular interest - Trusted Relays...
    http://wiki.apache.org/spamassassin/TrustedRelays
    Basically, by explicitly declaring your trusted_networks and internal_networks you both exclude the possibility of false ALL_TRUSTED flags and also optimise DNSBL lookups. These additional benefits are only applicable if Network Tests are enabled (otherwise no point in adding full info).
    At the least, trusted_networks should be set to your internal network range and your mail server's IP. The latter will not be required if it is behind a nat router since it will be part of the same LAN network. Otherwise the public IP for your mail server should also be added. Where internal_networks is not explicitly declared, this will default to the same networks as trusted_networks. However, it appears to be beneficial to network tests to separate out these two options and be more informative...
    "By giving SpamAssassin more info about your network setup, it can perform some tests better, increase accuracy, and reduce load."
    The advice, according to above links, is to add any known external trusted servers (such as secondary MX IPs) to trusted_networks. So in local.cf you could have...
    trusted_networks 192.168.0/24 111.234.567.23
    internal_networks 192.168.0/24
    ...where the 111 IP is an external secondary MX.
    [Question: should 127.0.0.1 be in these two also? I've not added it before and never noticed anything untoward but the SA links show it in one example.]
    By 'trusted server' this merely means a server which you trust to not be under control of spammers or an open relay. It may well relay spam on to you but the information which it puts into the headers about that piece of spam can be trusted. So the list does not need to be directly related to your domain.
    This information is valuable to SA since it both allows it to ignore doing network tests on the trusted relays and also identify the most recent 'untrusted' server in the chain (see 2nd link above). The latter is the most likely origin of any spam and therefore more attention can be paid to investigating this server. Additional network tests are made on this first untrusted server (additional helo tests are in std rule set).
    It seems to me that the additional 'work' in fully declaring these two options is worth the potential benefits. Anyone got any comments? (particularly about the inclusion of 127.0.0.1?)
    -david

    Hi David,
    I was working on this issue tonight as a result of the thread you mentioned. I found the information at http://wiki.apache.org/spamassassin/TrustPath a bit difficult to understand, so I appreciate your post about this.
    Ok, my trusted_networks is set to ...
    trusted_networks 192.168.0/24 192.168.1/24 127.0.0.1 69.49.170.8
    Here is my reasoning for the settings I've listed:
    I started looking at the headers of e-mails from the clients on my local network. I wanted to see "ALL_TRUSTED=-1.8" applied to anyone sending from my local networks.
    I've got two local networks connected by a VPN (192.168.0.x and 192.168.1.x). By listing 192.168.0/24 and 192.168.1/24, I could ensure that any client on either of my two local networks would be trusted. My server is behind a NAT, so I did not need to list its public IP.
    By listing 127.0.0.1, I could ensure that any mail sent from SquirrelMail (located on my server) would be trusted.
    69.49.170.8 is an external host that handles mailing list subscription requests from our web site. It needs to forward these subscription requests to our server as a trusted network, so I added it.
    In answer to your question about 127.0.0.1 being listed as a trusted_network, I added it because I wanted mail from SquirrelMail to be receive the "ALL_TRUSTED" designation. If you remove it, mail sent from SquirrelMail does not get the ALL_TRUSTED designation.
    Heretofore, I had not included the internal_networks parameter. However, based on your post ...
    Where internal_networks is not explicitly declared, this will default
    to the same networks as trusted_networks. However, it appears to be beneficial
    to network tests to separate out these two options and be more informative...
    "By giving SpamAssassin more info about your network setup, it can
    perform some tests better, increase accuracy, and reduce load."
    I added ...
    internal_networks 192.168.0/24 192.168.1/24
    Thanks for that suggestion.

  • Account lock & further deletion

    Hi guys, i need to know the effects/impacts of deleting user account from SAP for the terminated employees.
    Is it to the management to decide for the removal of accounts? Or what is the std. rule for locking & deleting an user account from the system?
    Pls advise.
    rgds,
    pri

    Hi,
    when you delete a user you would lose some part of the trail of his actions which might be an issue as per the compliance issues.
    So these ID's are locked and validity changed to the date of exit of that particular user so that we still have the user and can avoid him to login.
    So once we are pretty sure that the deletion of the ID's would not have any negative ramifications there are deleled.
    So its the top management's call as to how they want to address this particular issue and varies as per the firms policy.
    Normally a better approach would be to lock the ID's and end the validity date.
    Manohar

Maybe you are looking for

  • Text input action AS3

    I have a text input field on the timeline that I want the user to enter specific information in. When that information is correctly entered, I need the timeline to progress. I successfully used the following AS2, but I cant find corresponding code fo

  • How to make the Convert task to exit if there is Rejected data

    Hello, I try to develop a DTSX package for SQL 2005, with BPC 7.0 SP6. The package contains Convert step. I want to exit package execution if during the Convert step there is at least one Rejected data Problem: Convert task exists On Failure only if

  • Pasting Ken Burns  Into Clips Moves clip

    This has only happened a few times.   To save time, I paste the ken burns attributes into multiple selected clips.  I use the paste attributes command.  At times when I to that the clip itself is moved out of the visible movie frame.   I have only no

  • Repository browser not working - very slow

    Hi there started owb browser listener can login to see the various options but when click one e.g execution summary report - it is very slow and nothing appears - this used to work. Any ideas? Many Thanks

  • Stateless session's one method to call  two bmp's create method

    JSP calls one stateless session's one method and the method calls two bmps'           create method.           However, When the second bmp run the create operation, the exception           happens.           But the date that the first bmp insert is