Extracting values for characteristic on release strategy of Preq

hello
we have Preq release strategy based on classification and the release is based on amount. in the class, one of the characteristics contains the amount above which the strategy is being triggered: how can I extract all the values for all the strategies from this characteristic? is there a table for it?

Hi,
Please check the AUSP table for release strtegies and CAWN table for characteristics. Please check below link for additional information. Thanking you.
Release strategy tables

Similar Messages

  • Incorrect initial value for characteristic 0fiscyear in i_t_range

    Hi,
    While extracting the data from the source DSO to Target I got an error message like '' Incorrect initial value for characteristic 0fiscyear in i_t_range".
    what is the step should i take to resolve this?
    Thanks in Advance.

    Gurus
    I have the same problem with my ABAP code written in DTP filter.
    Can anyone please help what needs to be done , I am getting this error when I try to load the data to cube.

  • User Exit for Purchase Order Release Strategy

    Hi,
    I am a little new to this, how do I search for a user exit for purchase order release strategy (TCode ME29N).
    Thanks in advance.
    Mick

    Hi
    Check the following Exits and BADI for Pur Requisition
    Enhancement
    MEVME001 WE default quantity calc. and over/ underdelivery tolerance
    MM06E001 User exits for EDI inbound and outbound purchasing documents
    MM06E003 Number range and document number
    MM06E004 Control import data screens in purchase order
    MM06E005 Customer fields in purchasing document
    MM06E007 Change document for requisitions upon conversion into PO
    MM06E008 Monitoring of contr. target value in case of release orders
    MM06E009 Relevant texts for "Texts exist" indicator
    MM06E010 Field selection for vendor address
    MM06E011 Activate PReq Block
    MMAL0001 ALE source list distribution: Outbound processing
    MMAL0002 ALE source list distribution: Inbound processing
    MMAL0003 ALE purcasing info record distribution: Outbound processing
    MMAL0004 ALE purchasing info record distribution: Inbound processing
    MMDA0001 Default delivery addresses
    MMFAB001 User exit for generation of release order
    MRFLB001 Control Items for Contract Release Order
    AMPL0001 User subscreen for additional data on AMPL
    LMEDR001 Enhancements to print program
    LMELA002 Adopt batch no. from shipping notification when posting a GR
    LMELA010 Inbound shipping notification: Transfer item data from IDOC
    LMEQR001 User exit for source determination
    LMEXF001 Conditions in Purchasing Documents Without Invoice Receipt
    LWSUS001 Customer-Specific Source Determination in Retail
    M06B0001 Role determination for purchase requisition release
    M06B0002 Changes to comm. structure for purchase requisition release
    M06B0003 Number range and document number
    MEQUERY1 Enhancement to Document Overview ME21N/ME51N
    MELAB001 Gen. forecast delivery schedules: Transfer schedule implem.
    MEFLD004 Determine earliest delivery date f. check w. GR (only PO)
    MEETA001 Define schedule line type (backlog, immed. req., preview)
    ME590001 Grouping of requsitions for PO split in ME59
    M06E0005 Role determination for release of purchasing documents
    M06E0004 Changes to communication structure for release purch. doc.
    M06B0005 Changes to comm. structure for overall release of requisn.
    M06B0004 Number range and document number
    Business Add-in
    ME_PROCESS_REQ_CUST Enhancements for Processing Enjoy PReqs: Customer
    ME_PROCESS_REQ Enhancements for Processing Enjoy PReqs: Internal
    ME_PROCESS_PO_CUST Enhancements for Processing Enjoy Purchase Order: Customer
    ME_PROCESS_PO Enhancements for Processing Enjoy Purchase Order: Intern.
    ME_PROCESS_COMP Processing of Component Default Data at Time of GR: Custome
    ME_PO_SC_SRV BAdI: Service Tab Page for Subcontracting
    ME_PO_PRICING_CUST Enhancements to Price Determination: Customer
    ME_PO_PRICING Enhancements to Price Determination: Internal
    ME_INFOREC_SEND Capture/Send Purchase Info Record Changes - Internal Use
    ME_HOLD_PO Hold Enjoy Purchase Orders: Activation/Deactivation
    ME_GUI_PO_CUST Customer's Own Screens in Enjoy Purchase Order
    ME_FIELDSTATUS_STOCK FM Account Assignment Behavior for Stock PR/PO
    ME_DP_CLEARING Clearing (Offsetting) of Down Payments and Payment Requests
    ME_PURCHDOC_POSTED Purchasing Document Posted
    SMOD_MRFLB001 Control Items for Contract Release Order
    EXTENSION_US_TAXES Extended Tax Calculation with Additional Data
    ARC_MM_EKKO_WRITE BAdI: Enhancement of Scope of Archiving (MM_EKKO)
    ARC_MM_EKKO_CHECK BAdI: Enhancement of Archivability Check (MM_EKKO)
    MM_EDI_DESADV_IN Supplementation of Delivery Interface from Purchase Order
    MM_DELIVERY_ADDR_SAP Determination of Delivery Address
    ME_WRF_STD_DNG PO Controlling Reminder: Extension to Standard Reminder
    ME_TRIGGER_ATP Triggers New ATP for Changes in EKKO, EKPO, EKPV
    ME_TRF_RULE_CUST_OFF BADI for Deactivation of Field T161V-REVFE
    ME_TAX_FROM_ADDRESS Tax jurisdiction code taken from address
    ME_REQ_POSTED Purchase Requisition Posted
    ME_REQ_OI_EXT Commitment Update in the Case of External Requisitions
    ME_RELEASE_CREATE BAdI: Release Creation for Sched.Agrmts with Release Docu.
    ME_DEFINE_CALCTYPE Control of Pricing Type: Additional Fields
    ME_CHANGE_OUTTAB Enrich ALV Output Table in Purchasing
    ME_CHANGE_CHARACTER Customer-Specific Characteristics for Product Allocation
    ME_CCP_DEL_DURATION Calc. of Delivery Duration in CCP Process (Not in Standard)
    ME_CCP_BESWK_AUTH_CH BAdI for authorization checks for procuring plant
    ME_CCP_ACTIVE_CHECK BAdI to check whether CCP process is active
    ME_BSART_DET Change document type for automatically generated POs
    ME_BAPI_PR_CREATE_02
    ME_BAPI_PR_CREATE_01
    ME_BAPI_PO_CREATE_02
    ME_BAPI_PO_CREATE_01
    ME_BADI_DISPLAY_DOC BAdI for Internal Control of Transaction to be Invoked
    ME_ACTV_CANCEL_PO BAdI for Activating the Cancel Function at Header Level
    MEGUI_LAYOUT BAdI for Enjoy Purchasing GUI
    ME_CHECK_ALL_ITEMS Run Through Items Again in the Event of Changes in EKKO
    ME_COMMTMNT_REQ_RE_C Check of Commitment Relevance of Purchase Requisitions
    ME_COMMTMNT_REQ_RELE Check of Commitment Relevance of Purchase Requisitions
    ME_COMMTMNT_PO_REL_C Check for Commitment-Relevance of Purchase Orders
    ME_COMMTMNT_PO_RELEV Check for Commitment-Relevance of Purchase Orders
    ME_COMMITMENT_STO_CH BadI for checking if commitments for STOs are active
    ME_COMMITMENT_RETURN Commitment for return item
    ME_CIP_REF_CHAR Enables Reference Characteristics in Purchasing
    ME_CIP_ALLOW_CHANGE Configuration in Purchasing: Changeability Control
    ME_CIN_MM06EFKO Copy PO data for use by Country version India
    ME_CIN_LEINRF2V BADI for LEINRF03 excise_invoice_details
    ME_CIN_LEINRF2R BADI for CIN India - Delivery charges
    ME_CHECK_SOURCES Additional Checks in Source Determination/Checking
    ME_CHECK_OA Check BAdI for Contracts
    Reward points if useful
    Rgds,
    Naren

  • Badi for Purchase Requisition Release Strategy

    Can any help me to know about the BADI for Purchase Requisition Release Strategy .Is their any BADI to  control the PO Price for a PR release strategy
    Thanks for your help

    This badi is for schedule agreement ?
    BAdI: Release Creation for Scheduling Agreements with Release Documentation
    Use
    You can use this Business Add-In (BAdI) to influence release creation.
    This BAdI is used in the application component Scheduling Agreements (MM-PUR-OA-SCH).
    This BAdI includes the following methods:
    Change Data Before Release Creation (BEFORE_CREATION)
    Change Data After Release Creation (AFTER_CREATION)
    This BAdI is called during manual and automatic release creation.

  • In TXN CO03, extract value for field "To Confirm" under tab "Qty/Activity"

    Hi,
    Can anyone help to extract value for field "To Confirm" under tab "QTY/ACTIVITIES" in tansaction CO03 at operatin level. There are three Activiti (CC-Set-up,CC-Labor Time & CC-Var-OH) under table control Activities. I need value of the field "To Confirm" for CC-Labor Time.
    From where I can fetch this value,
    1. Is this field available in some table?
    2. Is there any FM with which the same can be extracted.
    3. Any other method?
    Regards,
    Bibhuti.
    Edited by: bibhuti kumar on Feb 20, 2008 6:16 AM

    Hi,
    pls use below table's and get detals you want
    AFKO - Order header details
    AFVC - Order operation details
    AFVV - Order operation value/date's/qty details
    the relation is below
    Step1: AFKO; AUFNR-->AFKO-AUFPL
    Step2: AFVC; AFKO-AUFPL = AFVC-AUFPL
    take filed to APLZL,VORNR
    Step3: AFVV;AFKO-AUFPL=AFVV-AUFPL, AFVC-AUFPL = AFVV-AUFPL
    take filed to MGVRG,LMNGA,XMNGA,VGW02
    Step4: (MGVRG - (LMNGA+XMNGA)) * VGW02
    hope this will solve your problem
    Regards,
    Sankaran

  • Extract value for Domain

    Hi
    I have to extract value for Domain Name attribute, Please give me the query to do it.
    Thanks lot in advance
    Murthy
    <?xml version="1.0" encoding="ISO-8859-1"?>
    <?Siebel-Property-Set EscapeNames="false"?>
    <SiebelMessage MessageId="1-Y4BH" LineItemCount="" IntObjectName="MH Order Item Integration" MessageType="Integration Object" IntObjectFormat="Siebel Hierarchical">
    <ListOfMhOrderItemIntegration>
    <OrderItem>
    <AccountExecID/>
    <ActionCode>Add</ActionCode>
    <AltRepID>20</AltRepID>
    <AddressRowId>1-4XL4-115</AddressRowId>
    <AttentionTo/>
    <CancelCode/>
    <CancelDate/>
    <City>Houston</City>
    <ContractDate/>
    <Country>USA</Country>
    <CreatedBy>SADMIN</CreatedBy>
    <CreatedDateTime>10/19/2005 09:40:50</CreatedDateTime>
    <CreditCardExpDate/>
    <CreditCardNumber/>
    <CreditCardType/>
    <CustomerNumber>5020047500</CustomerNumber>
    <EditionYear>2006</EditionYear>
    <GrossAmount>590</GrossAmount>
    <HoldBilling/>
    <HoldShipping/>
    <InceptionCode>N</InceptionCode>
    <LastUpdatedDateTime>10/19/2005 12:41:12</LastUpdatedDateTime>
    <LastYearTrackingNumber/>
    <LineAmount>590</LineAmount>
    <LineItemRowID>1-1DWIEK</LineItemRowID>
    <LineItemStatus>New</LineItemStatus>
    <ListingID>3803930</ListingID>
    <MigrationChildCode/>
    <MealeysSubId/>
    <MealeysPwd/>
    <MigrationType/>
    <OrderCanvassDate>10/19/2005 00:00:00</OrderCanvassDate>
    <OrderHeaderId>1-1DWHZU</OrderHeaderId>
    <OrderLastUpdatedBy>UMATTJA</OrderLastUpdatedBy>
    <OrderNumber>835905</OrderNumber>
    <OrderTaker>20</OrderTaker>
    <OrgID>2486393</OrgID>
    <POBox/>
    <PrimaryRepID>35</PrimaryRepID>
    <Producer>SIEBEL</Producer>
    <ProductCode>01807</ProductCode>
    <ProductContent>51</ProductContent>
    <ProductName>LHP Plus</ProductName>
    <PurchaseOrderNumber/>
    <Quantity>1</Quantity>
    <ReferenceNumber/>
    <ReinstatedDate/>
    <ReturnMessage>This URL already used by another organization.</ReturnMessage>
    <Revision>0</Revision>
    <RollupCount/>
    <ServiceAccountName>McEwing, David</ServiceAccountName>
    <ShippingCharges/>
    <SiebelAssetIntegrationId>1-1DWIEK</SiebelAssetIntegrationId>
    <SiebelID>2683171</SiebelID>
    <SiebelIntegrationId>1-1DWIEK</SiebelIntegrationId>
    <SiebelLineNumber>5</SiebelLineNumber>
    <SiebelLineNumber2/>
    <SignedBy/>
    <State>TX</State>
    <StateCode>48</StateCode>
    <StreetAddress1>3200 Southwest Freeway, 2355 Phoenix Tower</StreetAddress1>
    <Suite/>
    <TotalDiscountAmount>0</TotalDiscountAmount>
    <TrackingNumber>1-1DXOFH</TrackingNumber>
    <UnitPrice>590</UnitPrice>
    <ZipCode>77027</ZipCode>
    <TaxableFlg/>
    <SolRept/>
    <ListOfAttribute>
    <Attribute>
    <AttrProductCode>1812</AttrProductCode>
    <TrackingNumber>1-1DXOFS</TrackingNumber>
    <Name>Number of Attorneys</Name>
    <SiebelAttrName>100Number of Attorneys LHP Plus|1812</SiebelAttrName>
    <Value>1</Value>
    </Attribute>
    <Attribute>
    <AttrProductCode/>
    <TrackingNumber>1-1DXOFV</TrackingNumber>
    <Name>Domain Name</Name>
    <SiebelAttrName>103 Domain Name</SiebelAttrName>
    <Value>davidmcewinglaw.com</Value>
    </Attribute>
    <Attribute>
    <AttrProductCode/>
    <TrackingNumber>1-1DXOFR</TrackingNumber>
    <Name>Tag Line</Name>
    <SiebelAttrName>200 Tag Line</SiebelAttrName>
    <Value>Intellectual Property, Divisional Applications, Trademark, Patent, Copyright, Internet Law</Value>
    </Attribute>
    <Attribute>
    <AttrProductCode/>
    <TrackingNumber>1-1DXOFO</TrackingNumber>
    <Name>Template</Name>
    <SiebelAttrName>201Template Selection</SiebelAttrName>
    <Value>None</Value>
    </Attribute>
    <Attribute>
    <AttrProductCode/>
    <TrackingNumber>1-1DXOFN</TrackingNumber>
    <Name>Registration Type</Name>
    <SiebelAttrName>202Registration Type</SiebelAttrName>
    <Value>NEW</Value>
    </Attribute>
    <Attribute>
    <AttrProductCode/>
    <TrackingNumber>1-1DXOFW</TrackingNumber>
    <Name>Contact First Name</Name>
    <SiebelAttrName>250Contact First Name</SiebelAttrName>
    <Value>David</Value>
    </Attribute>
    <Attribute>
    <AttrProductCode/>
    <TrackingNumber>1-1DXOFU</TrackingNumber>
    <Name>Contact Last Name</Name>
    <SiebelAttrName>251Contact Last Name</SiebelAttrName>
    <Value>McEwing</Value>
    </Attribute>
    <Attribute>
    <AttrProductCode/>
    <TrackingNumber>1-1DXOFM</TrackingNumber>
    <Name>Contact eMail</Name>
    <SiebelAttrName>252Contact eMail</SiebelAttrName>
    <Value>[email protected]</Value>
    </Attribute>
    <Attribute>
    <AttrProductCode/>
    <TrackingNumber>1-1DXOFQ</TrackingNumber>
    <Name>Contact Fax</Name>
    <SiebelAttrName>2533Contact Fax</SiebelAttrName>
    <Value>713-514-9840</Value>
    </Attribute>
    <Attribute>
    <AttrProductCode/>
    <TrackingNumber>1-1DXOFP</TrackingNumber>
    <Name>Contact Phone</Name>
    <SiebelAttrName>253Contact Phone</SiebelAttrName>
    <Value>713-514-0137</Value>
    </Attribute>
    <Attribute>
    <AttrProductCode/>
    <TrackingNumber>1-1DXOFT</TrackingNumber>
    <Name>Site Name</Name>
    <SiebelAttrName>256URL</SiebelAttrName>
    <Value/>
    </Attribute>
    <Attribute>
    <AttrProductCode/>
    <TrackingNumber>1-1DXOFL</TrackingNumber>
    <Name>Future unique heads</Name>
    <SiebelAttrName>Future unique heads</SiebelAttrName>
    <Value/>
    </Attribute>
    </ListOfAttribute>
    </OrderItem>
    </ListOfMhOrderItemIntegration>
    </SiebelMessage>

    Once the problem is clearly stated the answer is simple...
    SQL> set serveroutput on
    SQL> declare
      2     myXML XMLType := xmlType(
      3  '<?xml version="1.0" encoding="ISO-8859-1"?>
      4  <?Siebel-Property-Set EscapeNames="false"?>
      5  <SiebelMessage MessageId="1-Y4BH" LineItemCount="" IntObjectName="MH Order Item Integration" MessageType="Integratio
    Format="Siebel Hierarchical">
      6     <ListOfMhOrderItemIntegration>
      7             <OrderItem>
      8                     <AccountExecID/>
      9                     <ActionCode>Add</ActionCode>
    10                     <AltRepID>20</AltRepID>
    11                     <AddressRowId>1-4XL4-115</AddressRowId>
    12                     <AttentionTo/>
    13                     <CancelCode/>
    14                     <CancelDate/>
    15                     <City>Houston</City>
    16                     <ContractDate/>
    17                     <Country>USA</Country>
    18                     <CreatedBy>SADMIN</CreatedBy>
    19                     <CreatedDateTime>10/19/2005 09:40:50</CreatedDateTime>
    20                     <CreditCardExpDate/>
    21                     <CreditCardNumber/>
    22                     <CreditCardType/>
    23                     <CustomerNumber>5020047500</CustomerNumber>
    24                     <EditionYear>2006</EditionYear>
    25                     <GrossAmount>590</GrossAmount>
    26                     <HoldBilling/>
    27                     <HoldShipping/>
    28                     <InceptionCode>N</InceptionCode>
    29                     <LastUpdatedDateTime>10/19/2005 12:41:12</LastUpdatedDateTime>
    30                     <LastYearTrackingNumber/>
    31                     <LineAmount>590</LineAmount>
    32                     <LineItemRowID>1-1DWIEK</LineItemRowID>
    33                     <LineItemStatus>New</LineItemStatus>
    34                     <ListingID>3803930</ListingID>
    35                     <MigrationChildCode/>
    36                     <MealeysSubId/>
    37                     <MealeysPwd/>
    38                     <MigrationType/>
    39                     <OrderCanvassDate>10/19/2005 00:00:00</OrderCanvassDate>
    40                     <OrderHeaderId>1-1DWHZU</OrderHeaderId>
    41                     <OrderLastUpdatedBy>UMATTJA</OrderLastUpdatedBy>
    42                     <OrderNumber>835905</OrderNumber>
    43                     <OrderTaker>20</OrderTaker>
    44                     <OrgID>2486393</OrgID>
    45                     <POBox/>
    46                     <PrimaryRepID>35</PrimaryRepID>
    47                     <Producer>SIEBEL</Producer>
    48                     <ProductCode>01807</ProductCode>
    49                     <ProductContent>51</ProductContent>
    50                     <ProductName>LHP Plus</ProductName>
    51                     <PurchaseOrderNumber/>
    52                     <Quantity>1</Quantity>
    53                     <ReferenceNumber/>
    54                     <ReinstatedDate/>
    55                     <ReturnMessage>This URL already used by another organization.</ReturnMessage>
    56                     <Revision>0</Revision>
    57                     <RollupCount/>
    58                     <ServiceAccountName>McEwing, David</ServiceAccountName>
    59                     <ShippingCharges/>
    60                     <SiebelAssetIntegrationId>1-1DWIEK</SiebelAssetIntegrationId>
    61                     <SiebelID>2683171</SiebelID>
    62                     <SiebelIntegrationId>1-1DWIEK</SiebelIntegrationId>
    63                     <SiebelLineNumber>5</SiebelLineNumber>
    64                     <SiebelLineNumber2/>
    65                     <SignedBy/>
    66                     <State>TX</State>
    67                     <StateCode>48</StateCode>
    68                     <StreetAddress1>3200 Southwest Freeway, 2355 Phoenix Tower</StreetAddress1>
    69                     <Suite/>
    70                     <TotalDiscountAmount>0</TotalDiscountAmount>
    71                     <TrackingNumber>1-1DXOFH</TrackingNumber>
    72                     <UnitPrice>590</UnitPrice>
    73                     <ZipCode>77027</ZipCode>
    74                     <TaxableFlg/>
    75                     <SolRept/>
    76                     <ListOfAttribute>
    77                             <Attribute>
    78                                     <AttrProductCode>1812</AttrProductCode>
    79                                     <TrackingNumber>1-1DXOFS</TrackingNumber>
    80                                     <Name>Number of Attorneys</Name>
    81                                     <SiebelAttrName>100Number of Attorneys LHP Plus|1812</SiebelAttrName>
    82                                     <Value>1</Value>
    83                             </Attribute>
    84                             <Attribute>
    85                                     <AttrProductCode/>
    86                                     <TrackingNumber>1-1DXOFV</TrackingNumber>
    87                                     <Name>Domain Name</Name>
    88                                     <SiebelAttrName>103 Domain Name</SiebelAttrName>
    89                                     <Value>davidmcewinglaw.com</Value>
    90                             </Attribute>
    91                             <Attribute>
    92                                     <AttrProductCode/>
    93                                     <TrackingNumber>1-1DXOFR</TrackingNumber>
    94                                     <Name>Tag Line</Name>
    95                                     <SiebelAttrName>200 Tag Line</SiebelAttrName>
    96                                     <Value>Intellectual Property, Divisional Applications, Trademark, Patent, Copyrig
    alue>
    97                             </Attribute>
    98                             <Attribute>
    99                                     <AttrProductCode/>
    100                                     <TrackingNumber>1-1DXOFO</TrackingNumber>
    101                                     <Name>Template</Name>
    102                                     <SiebelAttrName>201Template Selection</SiebelAttrName>
    103                                     <Value>None</Value>
    104                             </Attribute>
    105                             <Attribute>
    106                                     <AttrProductCode/>
    107                                     <TrackingNumber>1-1DXOFN</TrackingNumber>
    108                                     <Name>Registration Type</Name>
    109                                     <SiebelAttrName>202Registration Type</SiebelAttrName>
    110                                     <Value>NEW</Value>
    111                             </Attribute>
    112                             <Attribute>
    113                                     <AttrProductCode/>
    114                                     <TrackingNumber>1-1DXOFW</TrackingNumber>
    115                                     <Name>Contact First Name</Name>
    116                                     <SiebelAttrName>250Contact First Name</SiebelAttrName>
    117                                     <Value>David</Value>
    118                             </Attribute>
    119                             <Attribute>
    120                                     <AttrProductCode/>
    121                                     <TrackingNumber>1-1DXOFU</TrackingNumber>
    122                                     <Name>Contact Last Name</Name>
    123                                     <SiebelAttrName>251Contact Last Name</SiebelAttrName>
    124                                     <Value>McEwing</Value>
    125                             </Attribute>
    126                             <Attribute>
    127                                     <AttrProductCode/>
    128                                     <TrackingNumber>1-1DXOFM</TrackingNumber>
    129                                     <Name>Contact eMail</Name>
    130                                     <SiebelAttrName>252Contact eMail</SiebelAttrName>
    131                                     <Value>[email protected]</Value>
    132                             </Attribute>
    133                             <Attribute>
    134                                     <AttrProductCode/>
    135                                     <TrackingNumber>1-1DXOFQ</TrackingNumber>
    136                                     <Name>Contact Fax</Name>
    137                                     <SiebelAttrName>2533Contact Fax</SiebelAttrName>
    138                                     <Value>713-514-9840</Value>
    139                             </Attribute>
    140                             <Attribute>
    141                                     <AttrProductCode/>
    142                                     <TrackingNumber>1-1DXOFP</TrackingNumber>
    143                                     <Name>Contact Phone</Name>
    144                                     <SiebelAttrName>253Contact Phone</SiebelAttrName>
    145                                     <Value>713-514-0137</Value>
    146                             </Attribute>
    147                             <Attribute>
    148                                     <AttrProductCode/>
    149                                     <TrackingNumber>1-1DXOFT</TrackingNumber>
    150                                     <Name>Site Name</Name>
    151                                     <SiebelAttrName>256URL</SiebelAttrName>
    152                                     <Value/>
    153                             </Attribute>
    154                             <Attribute>
    155                                     <AttrProductCode/>
    156                                     <TrackingNumber>1-1DXOFL</TrackingNumber>
    157                                     <Name>Future unique heads</Name>
    158                                     <SiebelAttrName>Future unique heads</SiebelAttrName>
    159                                     <Value/>
    160                             </Attribute>
    161                     </ListOfAttribute>
    162             </OrderItem>
    163     </ListOfMhOrderItemIntegration>
    164  </SiebelMessage>'
    165  );
    166    result varchar2(64);
    167  begin
    168     select extractValue(value(attr),'/Attribute/Value')
    169       into result
    170       from table(xmlsequence(extract(myXML,'/SiebelMessage/ListOfMhOrderItemIntegration/OrderItem/ListOfAttribute/Att
    171      where existsNode(value(attr),'/Attribute[Name="Domain Name"]') = 1;
    172    dbms_output.put_line('Result = ' || result);
    173  end;
    174  /
    Result = davidmcewinglaw.com
    PL/SQL procedure successfully completed.
    SQL>This assumes that there is only one Attribute element with a Name node whose value is "Domain Name". If there was more than one such node you would have to use a cursor and process the results in loop.

  • Precautions to be taken before going for new PR Release strategy

    Dear all,
    We are going to implement release strategy with classification at item level release. Current process in our company release strategy without classification at item level release was implemented and its Production for past 3 years.
    Need your advice on
    1)If we go for new release strategy as off  with existing release strategy -what are the precautions to be taken before implementing new strategy - any problem will happen to existing data with old releases, which already release, yet to release?
    2)Once after implementing the new releases, the PR with old release strategy (which is not release yet)u2026does this will trigger new release?
    3)Any other which I missed out, please suggest me
    Thanks
    RS

    Hi,
    It is better to release all existing PRs using your current procedure without classificaton and clean up.
    If you impliment procedure with classification, It depends on the parameters like Plant, value, purchasing group you are going to use in the strategy. Also you may decide whether to have overall req release or item level release of PR by having diffrent release groups.
    REgards
    Ram
    Edited by: ramachandran subramanian on Feb 18, 2009 7:00 AM

  • Creating Roles for Purchase Req. release strategy with classification

    Hi friends,
    Since I have created Purchase req rel strategy where I have four release strategy
    1. For Plant 1 When value <= 5000 (Officer) will release , release code 01 release release strategy r1 and rel code L1
    2 For Plant 1 When value >= 5000 (Manager) will release , release code 01 release release strategy r2and rel code L2
    Now the manager will have 2 release code,if  officer is absent he could release the requisition.
    Same has to be done for plant 2
    The release Group and code needs to be assigned to the Roles , could anybody tell  me  where i could know about roles and will be able to create roles and assign authorisation objects to the Roles , and release group and code to the enduser.
    though its a basis job , since I have no idea , I mean I have never worked with Roles ,as now I have created the Release strategy with classification I need to assign authorisation objects to the Roles as I have four release strategy
    1. For Plant 1 lower value of requisition 1 codeL1(Officer)
    2  For higher value of requisition 2 code say Li and L2(Manager)
    Manager should have 2 codes if  officer is absent he could release
    Same has to be done for Plant 2
    Thanks N Regards
    Siddhartha

    Hii,
    Steps:
    1) Create a Role
    2) Add the authorization Object  M_EINK_FRG by taking the manual option
    3) Assign Release Code and Release Grp
    4) Assign the Role to the User ID which has the authorization of the Release Code and Grp.
    Regards,
    Kumar

  • PO user exit for payment terms release strategy

    Hi friends,
    My requirement is to any changes to Payement terms in PO should trigger the re-release of the po....
    Plz. explain... How to proceed...
    which user exit i have to use........
    Thanks in advance,
    Navin.....

    My requirement is after changing of payment terms my release strategy is not changing for released po... i want to reset it for re-release after changes made to po changes....... which user exit i should should......or any other alternative....
    Rgds,
    Navin

  • External mail for workflow of release strategy for PO

    Dear All,
    I have configured the workflow of two step release strategy for purchase order and the internal mail is getting generated in the sap business workplace with the error message SWF_RUN 594 this i have taken care with SWE2 with changing the settings of "Behaviour upon error feedback" from "default" to "do not change linkage"
    Now the requiremnt is that the message has to be send to first level releaser through external mail and once first level release the PO external mail should be send to second level releaser.
    Please help me with the configuration step that is to be done
    Thanks in advance
    Naveen Singh

    Schedule the report Rswuwfml2. this will send workitem from sap inbox to respective user external mail id maintain in user master.

  • Challenge for release strategy in Preq

    hi all.
    our maintenance department requested a very specific release strategy for purchase requisitions with account assignment F (workorder).
    their release is based on several factors:
    1) amount: 0>2000 it must be released by the main work center which of course, depends on what is on the workorder and can be one of 3 (WC1, or WC2, or WC3)
    2) amount 2001>6250 it must be released by the following:
    WC1and/or Maintenance manager
    or
    WC2 and/or maintenace manager
    or
    WC3 and/or maintenance manager.
    the and/or mean that if WC1/2/3 releases, the maintenance manager will still need to release but if the maintenance manager releases first the Preq is released and there is no further need to release by WCn.
    anything >6250 must be released by the maintenance manager.
    our release strategy is with classification and we will use a user exit to determine which WC is being used and needs to release but i have a problem with point 2: how can i set the strategy in such a way that it can perform the release and/or?
    can someone help?

    Hi Alisa,
                 Your Requirement is very Complex,
    first thing if you want to have the Release strategy for the Account Assignment, you need to have that Characteristics in the class, and make sure that same rule is followed by all the Other PR, directly created.
    Second thing if you say that any thing less then 2000 should be released by the Main Work Center responsible person, which you have maintained by the user Exit, there must b a cross check that the person belonging to one work center should not be allowed to release the PR being generated in other Main Work Center.
    for that you need to have different Release codes assigned to the user in the roles.
    for any thing >2000and <6250, you need the WC1 and Maintenance Manager should release, but only Maintenance manager releases then also the PR should be released,
    Question: in above case what is the need of the WC1 or WC2 or WC3, let it be released by Manager only
    Please revert back.
    Regards,
    Yawar Khan

  • Issue in IP - Entering value for Characteristic object

    Hi Expert,
    I have a requirement where the input has to be unabled for characteristic objects through IP template.
    I did the development as per the blog:
    http://scn.sap.com/blogs/Christopher.sapbw/2012/12/25/master-data-planning-with-sap-integrated-planning-sap-ip
    The issue is the development should have been done by using Super class CL_RSMD_RS_BW_SPEC. But could not use it as super class as i could not modify the methods in this case. Instead i made a copy of this class and did some modifications to the class. The class is not working for me. Its throwing the following error.
    Please let me know if you have come across similar issue, and how to resolve it.
    Thanks,
    Anupama

    Hi Anass,
    I was able to solve the issue partially. Not getting the error now, but i am still not able to save the entered data back to the real time cube. I am using the analysis office for my development and using the standard save button on Analysis office.
    Please help.
    Thanks,
    Anupama

  • Workflow for purchase requisition release strategy

    Hi all,
    I need an urgent help on Workflow for Purchase Requisition Release. The requirement is that when a purchase requisition with a given combination (Purchasing Group, Material Group and Account Assignment Category) is created and saved, it should trigger a workflow for approval of release or rejection to one specific business manager. If he dont responds in 2 days, it should be sent to other business manager. If any one of them releases the requisition, it should send a mail to the requestor that the requisition is released. And if it is rejected, then also a mail to be sent to the requester informing that his requisition is rejected...
    Can anyone take some pain and guide me step by step procedure to implement this or to use any existing one.... I know its BUS2009 thats used in this but really dont know how to implement it properly.
    Its urgent...
    Edited by: Hima on Apr 11, 2008 12:45 PM

    Check this link
    http://help.sap.com/saphelp_47x200/helpdata/en/04/92762546f311d189470000e829fbbd/frameset.htm
    Thanks
    Arghadip

  • New release strategy / Old PReqs

    Hi,
    New release strategy has been configured to be active only for purchase requisitions with account assignment cat. F (PReqs coming from work order). In the other words every time when Preq is automatically created from work order new release strategy comes up. So far so good.
    But problem appears when user opens old work order where Service Purchase Requisition exist with old release strategy. After saving work order, without making any changes, new release strategy comes up and Preq status changes from 'Release Completed' to 'In Release'.
    Do you know what causes mentioned system behavior? Why release strategy is changed only for old service Preqs not for Preqs which contains non stock components?
    Many thanks in advance for your clues.
    Regards,
    Grzegorz

    Hi,
    Release strategy will trigger for creating and chenging the PR. If you want to restrict the PR release strategy for change mode, create (select if any one is there) authorization object for PR change mode in SU22. Create a role in PFCG and assign the authorization object to this. In SU01 assign this role to users or group of users. This will resolve your issue. But when you want to change the PR and retrigger the release strategy means won;t work out. In your case after going to change mode and saving the release strategy triggered. Its a sap standard behaviour. If you want to see PR goto ME53N instead of ME52N. If you goto ME52N Don't select save button if no changes are there. Ultimately no new release strategy will trigger. I hope this will resolve your issue. Thanking you.

  • Apply release strategy to STO PO same as normal PO

    Hi Expert,
    my user requested to have release strategy for STO (stock transport order) as the same practise as normal PO. So if they want to use the same release strategy as in normal PO, is it means that only need to add PO document type (for STO) to the release strategy? That's it?
    Thanks.

    Hi,
    It depends upon the characteristics you presently have for existing release strategy.  If you have total PO value as one of the criteriion, then you may have to go for new release strategy because generally conditions tab will not come for line items with item cateogry U.
    If the above situation is not relevant for your case, then you need to add the STO PO document type in the characteristics and assign the value for the particular release strategy using CL20N.
    Regards,

Maybe you are looking for