PO release startegy "common issue"

if release strategy cirtera contains item level characterisitc then if po contains multiple line item with differnet values agains that char. then system does not blocks the PO and for time being let us say PLANT / MAterial group as char.
now this issue is encountered by every one but i could not find the solution for this (i know the reason behind this issue but i dont know the precise solution some consultants say to maintain the blank value in char  value but i dont think system accepts blank value for char like plant/material group)
i hope to get some soild reply

so finally this is the solution for the issue
Unfortunately there is no mechanism like entering a blank or * in order to make classification understand this characteristic is not relevant.
The characteristic and its values will always been taken in consideration.
In case you use a 'non-aggregated' field in your release strategy you need to enter all possible values for the corresponding characteristic (as a range - just in case of numeric characteristics).
Example: You use item-wise release strategy for purchase requisitions
  and the plant is used in the release strategy (characteristic
  CEBAN-WERKS).
  Release strategy determination will be processed item by item.
  There will always be just one value for the plant (from the current
  item), multiple values and thus aggregation is not possible.
  In this case you have to enter all possible values for the
  characteristic CEBAN-WERKS.
In case you use an 'aggregated' field in your release strategy (which is possible for overall release strategy for PRs and release strategy for POs) and multiple values are used for that field on a purchasing document, you can use a blank value for the corresponding characteristic if you'd like the release strategy be applied.
Example: You use release strategy for a PO and the plant is one of the
  relevant fields (characteristic CEKKO-WERKS).
  You enter a first PO item with plant 0001 and a second item with plant
  0002.
  Since there are multiple values for the plant the system will
  'aggregate' to blank value and use blank value for searching for a
  release strategy.
  Since you have maintained a blank value for characteristic
  CEKKO-WERKS the system will find the corresponding release strategy.
In this case please pay attention to note 732566.
It causes an error in case blank values are used for release strategies.
Even when the long text just talks about process orders the impact of the side effect is more general.
Please take care note 754178 is implemented, it corrects note 732566.

Similar Messages

  • After updating my iPhone 4 to iOS7, the controls on the headset are not working anymore. However, the controls are working on my friend's iPhone 5. Is this a common issue?

    After updating my iPhone 4 to iOS7, the controls on the headset are not working anymore. However, the controls are working on my friend's iPhone 5. Is this a common issue?

    ofel wrote:
    After updating my iPhone 4 to iOS7, the controls on the headset are not working ..
    Try This...
    Close All Open Apps... Sign Out of your Account... Perform a Reset... Try again...
    Reset  ( No Data will be Lost )
    Press and Hold the Sleep/Wake Button and the Home Button at the Same Time...
    Wait for the Apple logo to Appear...
    Usually takes about 15 - 20 Seconds... ( But can take Longer...)
    Release the Buttons...

  • Common issues with BW environment

    Hello Experts,
    could you please mention all teh common issues faced in BW environment with the solution available.
    I have many issues and I wante dto know whether all teh teams face the same.
    This would a good oppurtunity to have everything in one thread.
    Thanks and regards
    meps

    Hi,
    We will have somany issues plz check some of them
    1. DTP Failure
    Select the step-> right click and select “Display Message”-> there we will get the message which gives the reason for ABEND.
    A DTP can failure due to following reasons, in such case we can go for restarting the job.
    System Exception Error
    Request Locked
    ABAP Run time error.
    Duplicate records
    Erroneous Records from PSA.
    Duplicate records:            In case of duplication in the records, we can find it in the error message along with the Info Provider’s name. Before restarting the job after deleting the bad DTP request, we have to handle the duplicate records. Go to the info provider -> DTP step -> Update tab -> check handle duplicate records -> activate -> Execute DTP. After successful competition of the job uncheck the Handle Duplicate records option and activate. DTP Log Run:
    If a DTP is taking log time than the regular run time without having the back ground job, then we have to turn the status of the DTP into Red and then delete the DTP bad request (If any), repeat the step or restart the job.
    Before restarting the Job/ repeating the DTP step, make sure about the reason for failure.
    If the failure is due to “Space Issue” in the F fact table, engage the DBA team and also BASIS team and explain them the issue. Table size needs to be increased before performing any action in BW. It’ll be done by DBA Team. After increasing the space in the F fact table we can restart the job.
    Erroneous Records from PSA:      When ever a DTP fails because of erroneous records while fetching the data from PSA to Data Target, in such cases data needs to be changed in the ECC. If it is not possible, then after getting the approval from the business, we can edit the Erroneous records in PSA and then we have to run the DTP. Go to PSA -> select request -> select error records -> edit the records and save.Then run the DTP. 2.      INFO PACKAGE FAILURE: The following are the reasons for Info Pack failure.
    Source System Connection failure
    tRFC/IDOC failure
    Communication Issues
    Processing the IDOC Manually in BI
    Check the source system connection with the help of SAP BASIS, if it is not fine ask them to rebuild the connection. After that restart the job (Info Pack).
    Go to RSA1 -> select source system -> System -> Connection check.
    In case of any failed tRFC’s/IDOC’s, the error message will be like “Error in writing the partition number DP2” or “Caller 01, 02 errors”. In such case reprocess the tRFC/IDOC with the help of SAP BASIS, and then job will finish successfully.
    If the data is loading from the source system to DSO directly, then delete the bad request in the PSA table, then restart the job
    Info Pack Long Run: If an info pack is running long, then check whether the job is finished at source system or not. If it is finished, then check whether any tRFC/IDOC struck/Failed with the help of SAP BASIS. Even after reprocessing the tRFC, if the job is in yellow status then turn the status into “Red”. Now restart / repeat the step. After completion of the job force complete.
    Before turning the status to Red/Green, make sure whether the load is of Full/Delta and also the time stamp is properly verified.
    Time Stamp Verification:
    Select Info Package-> Process Monitor -> Header -> Select Request -> Go to source System (Header->Source System) -> Sm37-> give the request and check the status of the request in the source system -> If it is in active, then we have to check whether there any struck/failed tRFC’s/IDOC’s If the request is in Cancelled status in Source system -> Check the Info Pack status in BW system -> If IP status is also in failed state/cancelled state -> Check the data load type (FULL or DELTA) -> if the status is full then we can turn the Info Package status red and then we can repeat/restart the Info package/job. -> If the load is of Delta type then we have to go RSA7 in source system-> (Compare the last updated time in Source System SM37 back ground job)) Check the time stamp -> If the time stamp in RSA7 is matching then turn the Info Package status to Red -> Restart the job. It’ll fetch the data in the next iterationIf the time stamp is not updated in RSA7 -> Turn the status into Green -> Restart the job. It’ll fetch the data in the next iteration.
    Source System
    BW System
    Source System RSA7
    Source System SM37
    Action
    I/P Status RED(Cancelled)
    I/P Status (Active)
    Time stamp matching with SM37 last updated time
    Time stamp matching with RSA7 time stamp
    Turn the I/P Status into Red and Restart the Job
    I/P Status RED(Cancelled)
    I/P Status (Cancelled)
    Time stamp matching with SM37 last updated time
    Time stamp matching with RSA7 time stamp
    Turn the I/P Status into Red and Restart the Job
    I/P Status RED(Cancelled)
    I/P Status (Active)
    Time stamp is not  matching with SM37 last updated time
    Time stamp is not matching with RSA7 time stamp
    Turn the I/P status into Green and Restart the job
    I/P Status RED(Cancelled)
    I/P Status (Cancelled)
    Time stamp is not  matching with SM37 last updated time
    Time stamp is not matching with RSA7 time stamp
    Turn the I/P status into Green and Restart the job
    Processing the IDOC Manually in BI:
    When there is an IDOC which is stuck in the BW and successfully completed the background job in the source system, in such cases we can process the IDOC manually in the BW. Go to Info Package -> Process Monitor -> Details -> select the IDOC which is in yellow status(stuck) -> Right click -> Process the IDOC manually -> it’ll take some time to get processed.******Make sure that we can process the IDOC in BW only when the back ground job is completed in the source system and stuck in the BW only.   3.      DSO Activation Failure: When there is a failure in DSO activation step, check whether the data is loading to DSO from PSA or from the source system directly. If the data is loading to DSO from PSA, then activate the DSO manually as follows
    Right click DSO Activation Step -> Target Administration -> Select the latest request in DSO -> select Activate -> after request turned to green status, Restart the job.
    If the data is loading directly from the source system to DSO, then delete the bad request in the PSA table, then restart the job
    4.      Failure in Drop Index/ Compression step: When there is a failure in Drop Index/ compression step, check the Error Message. If it is failed due to “Lock Issue”, it means job failed because of the parallel process or action which we have performed on that particular cube or object. Before restarting the job, make sure whether the object is unlocked or not. There is a chance of failure in Index step in case of TREX server issues. In such cases engage BASIS team and get the info reg TREX server and repeat/ Restart the job once the server is fixed. Compression Job may fail when there is any other job which is trying to load the data or accessing from the Cube. In such case job fails with the error message as “Locked by ......” Before restarting the job, make sure whether the object is unlocked or not.   5. Roll Up failure: “Roll Up” fails due to Contention Issue. When there is Master Data load is in progress, there is a chance of Roll up failure due to resource contention. In such case before restarting the job/ step, make sure whether the master data load is completed or not. Once the master data load finishes restart the job.   6. Change Run – Job finishes with error RSM 756       When there is a failure in the attribute change run due to Contention, we have to wait for the other job (Attribute change run) completion. Only one ACR can run in BW at a time. Once the other ACR job is completed, then we can restart/repeat the job. We can also run the ACR manually in case of nay failures. Go to RSA1-> Tool -> Apply Hierarchy/Change Run -> select the appropriate Request in the list for which we have to run ACR -> Execute. 7. Transformation In-active: In case of any changes in the production/moved to the production without saving properly or any modification done in the transformation without changing, in such cases there is a possibility of Load failure with the error message as “ Failure due to Transformation In active”. In such cases, we will have to activate the Transformation which is inactive. Go to RSA1 -> select the transformation -> Activate In case of no authorization for activating the transformation in production system, we can do it by using the Function Module - RSDG_TRFN_ACTIVATE Try the following steps to use the program "RSDG_TRFN_ACTIVATE” here you will need to enter certain details:Transformation ID: Transformation’s Tech Name (ID)Object Status: ACTType of Source: “Source Name”Source name: “Source Tech Name”Type of Target: Target NameTarget name: “Target Tech Name”
    Execute. The Transformation status will be turned into Active.
    Then we can restart the job. Job will be completed successfully.
         8. Process Chain Started from the yesterday’s failed step:
    In few instances, process chain starts from the step which was failed in the previous iteration instead of starting from the “Start” step.
    In such cases we will have to delete the previous day’s process chain log, to start the chain form the beginning (from Start variant).
    Go To ST13-> Select the Process Chain -> Log -> Delete.
    Or we can use Function Module for Process Chain Log Deletion: RSPROCESS_LOG_DELETE.
    Give the log id of the process chain, which we can get from the ST13 screen.
    Then we can restart the chain.
    Turning the Process Chain Status using Function Module:
    At times, when there is no progress in any of the process chains which is running for a long time without any progress, we will have to turn the status of the entire chain/Particular step by using the Function Module.
    Function Module: RSPC_PROCESS_FINISH
    The program "RSPC_PROCESS_FINISH" for making the status of a particular process as finished.
    To turn any DTP load which was running long, so please try the following steps to use the program "RSPC_PROCESS_FINISH" here you need to enter the following details:
    LOG ID: this id will be the id of the parent chain.
    CHAIN: here you will need to enter the chain name which has failed process.
    TYPE: Type of failed step can be found out by checking the table "RSPCPROCESSLOG" via "SE16" or "ZSE16" by entering the Variant & Instance of the failed step. The table "RSPCPROCESSLOG" can be used to find out various details regarding a particular process.
    INSTANCE & VARIANT: Instance & Variant name can be found out by right clicking on the failed step and then by checking the "Displaying Messages Options" of the failed step & then checking the chain tab.
    STATE: State is used to identify the overall state of the process. Below given are the various states for a step.
    R Ended with errors
    G Successfully completed
    F Completed
    A Active
    X Canceled
    P Planned
    S Skipped at restart
    Q Released
    Y Ready
    Undefined
    J Framework Error upon Completion (e.g. follow-on job missing)
    9. Hierarchy save Failure:
    When there a failure in Hierarchy Save, then we have to follow the below process...
    If there is an issue with Hierarchy save, we will have to schedule the Info packages associated with the Hierarchies manually. Then we have to run Attribute Change Run to update the changes to the associated Targets. Please find the below mentioned the step by step process...
    ST13-> Select Failed Process Chain -> Select Hierarchy Save Step -> Rt click Display Variant -> Select the info package in the hierarchy -> Go to RSA! -> Run the Info Package Manually -> Tools -> Run Hierarchy/Attribute Change Run -> Select Hierarchy List (Here you can find the List of Hierarchies) -> Execute.

  • Release Startegy for Item Category

    Hi ,
    Can we have a release startegy for PO for Charcetrstic Item category.
    It do not have any reference in in Table  CEKKO for any field.
    Can you tell me how can I activate the item category as a charcetrstic value in PO release startegy.
    Thanks,
    Lekhram

    PO release strategy always work at the header level but if oyu want to add the item level field as a char (in your case Item category) than you need use the user exit to insert the field in CEKKOZZ include of the CEKKO structure.
    Use the user exit M06E0004 to insert your field in CEKKOZZ include.
    once you get the field in this include then create the Char and use in classification.
    But make sure one thing is that
    Suppose you create the first line item of PO with Item category D and than you insert the second line with item category L and your release stratey doesn't have the both the item category than you are in problem
    Or suppose your first line has blank item category and second one has item category than also you will have issue.
    so make sure you create the PO for same item category without any othe combination to work with release.

  • Release Startegy

    Hi,
    We have configured PO release strategy by taking characters as Plant, Document Type, Value & Material Group.
    To be clear release is working fine when we consider a single material in line item of PO.
    We have 60 material groups and the release startegy is common for the material groups from  1 to 50 and the remaining 10 material groups 51 to 60 have different release strategy.
    If I create a PO with the material group from 1 - 50 i.e. two or theree materials which belong different material groups the release is not applied for that PO.
    For the same materials  if I create PO for individual material i.e. only single material group the release is applied.
    The release for PO isconfigured at header level. but the material groups are at item level.
    Thanks & Regards
    Sachin

    Hi Sachin,
    PO release strategy is only in header level not item level. So u should not consider Plant & Material Group as both the fields are in Item level.
    Our release strategy willl work if the palnt & material groups are same for all the line items.
    If there are multiple combination of plant & material group then release strategy won't affect.
    Reward points if its helpful to you.
    Sangram

  • PR Release startegy

    PR release startegy  should be flexible so that if we add any of the parameters, the program should follow the rules. The parameters that can be changed are:
    1. Document Types
    2. Project Types (We will need a custom table)
    3. Plants Groups
    4. Threshold Amounts
    The routing of the Purchase requisition approval is primarily based on the amount on the requisition, the Plant, and the department the requisitioner belongs to.
    In standard sap we have static parameters for release staregy, but here requiremnet is dynamic, when ever you chnage any of the parameters the syatem should adapt those chnages and the existing rules must apply for new one.

    Why would you change Doc. Type?
    If your requirements are not firmed than you should not raise requisition.
    No matter how dynamic your business is, requisition raised for a particular requirement should not vanish or change in a day or so.
    Practically speaking, it seems your supply chain is not process driven.
    For such scenarios you should allow to create POs directly once the requirements are firmed and aprovals covered for POs only.
    Regards,
    Dakshesh

  • Hello dps team,  A few weeks ago we renewed our dps licence. Now we want to release our newest issue but we can't. Following error message appears "At the attempt to release the folio creates an error. The process could not be started. Please try again la

    Hello dps team,
    A few weeks ago we renewed our dps licence. Now we want to release our newest issue but we can't. Following error message appears "At the attempt to release the folio creates an error. The process could not be started. Please try again later."
    Is there a problem with our dps version or any maintenance work at the servers from Adobe?
    Best,
    Oliver

    Hi Oliver,
    Please login to your DPS dashboard and contact support by clicking "Contact support" at the bottom left
    Thanks
    Lohrii

  • Release startegy for service PO

    Hi,
    Can you people help me out with release startegy for Service PO and service entry sheet?
    Regards,
    Satyendra

    Hi,
    Please refer below mention format.
    SPRO -> Material Management -> Purchasing -> Purchase Order -> Release Procedure for Purchase Orders.
    Three steps involved in release process of purchase order.
    1) Edit Characteristic: -
    Create characteristic for release purchase order. If you want to release purchase order on purchasing group base. So you can create characteristic for purchasing group. Take reference of CEKKO structure and BKGRP field for purchasing group in additional data of characteristic. E.g :- Purchasing group - BKGRP
    2) Edit Class: -
    After creation of characteristic, create class for release purchase order. In which you can take reference of
    Class Type: - 032,
    Status: - Release,
    Class group: - Release strategy class,
    And put reference of your characteristic, which are created by you in first step.
    E.g: - Class u2013 REL_PO
    3)Define Release Procedure of purchase order: -
    In this step four processes involved.
    1) Release Groups
    2) Release Codes
    3) Release indicator
    4) Release Strategies
    1) Release Group: - In which you can define release strategy group
    For Exa.: - Release group : - 01,Release object: - 01, Class: - REL_PO.
    2) Release code: - In which you can define release code. Enter value as
    Release group: - 01,release code: -01 u2013 Purchase Head,
    Release group: -01, release code: - 02 u2013 Auditor.
    3) Release indicator: - In this step you have to define release indicator.
    Like X u2013 Blocked, I u2013 Under process, S u2013 Release.
    4) Release Strategy: - This is the final step for release strategy.
    Assign release code 01, 02.
    Click on release prerequisites, select 02 u2013 check box and click on continue.
    Click on release status button, enter release indicator X, I, S and click continue
    Click on classification button, Enter values of purchasing group for which you want to created release strategy.
    Note: - Create characteristics for service order document type in CT04.
    Regards,
    Mahesh Wagh

  • Common Issues in IDOC/EDI

    Hi can some one please tell me the most common issues faced while setting up output detrmination through EDI in SD and also most common issues faced once EDI is configured..Please dont post Output detremination configuration process as i am aware of it.I am Concerned about the challenges and issues faced while setting up EDI and issues once EDI is configured (In SD point of view) .
    Thanks,
    Babu.
    Edited by: babu madina on May 29, 2008 1:57 PM

    Hi San Rao,
    1.Has the data request reached the SAP R/3..?
    -check for the queue entries in the  CRM out bound- SMQ1.
    -check the destination for R/3 or ECC in CRM-SM59.
    2.Has the data been extracted in R/3..?
    -check for the short dumps in ST22 in R/3
    3.Has the data been sent to the CRM..?
    -check for the queue entries in the qRFC out bound queue- SMQ1.
    4.If the the block number in the down load monitor shows 0 blocks in R3AM1 check the following
    - check the destination for CRM in R/3- SM59.
    -check which consumer is used for the object in the object management.
    -check the table CRMCONSUM in R/3 if the consumer is active.
    -check for the given consumer in table CRMFCPAR in R/3 if an entry exists for the object.
    5.Has the data reached CRM..?
    -check for the queue entries in the CRM inbound queue-SMQ2
    -check in the flow trace SMW01 if there are Bdocs in error state.
    -check for the short dumps in ST22 in CRM.
    6.Check the table CRMFCPAR
    -Table CRMFCPAR is valuated in the way that an entryfor a specific objectwill always be taken if it exists. If no specific entry exists, an entry with the object name ' * ' will be taken.the same goes for load type. If no entry exists, the initial load will be roll back to SMQ1 in CRM with a sysfail saying that no CRM is connected.
    -If the flag 'DISCARDDAT is set to 'X' , no data is sent.
    7. Status of the queue entries
    -Queue name for a initial load start with R3AI.
    -If queue entries exist in status READY, check SMQR (for SMQ1) orSMQR(for SMQ2). If the queue entries exists with the status SYSFAIL, analyse the error and restart the queue.
    -If queue entries exists in the status 'RUNNING' wait for the load to finish.
    -Never delete a queue entry manually.
    Reward points if its helpful.
    Regards
    Nadh.

  • External program to reset release startegy

    Hi All,
    Can anyone tell me how to reset release startegy from an external program. I understand that there are some exits avaialable to do it. I dont want to add my logic in an exit. Based on my program conditions I need to reset the release startegy of the P.O.
    Any Bapi of FM that is available.
    Thanks,
    Anupma

    BAPI_PO_RESET_RELEASE soved the probelm. U need to copy and remove std. check and it will work fine.
    Thanks,
    Anupma

  • Purchase order release startegy

    Dear Experts,
    We have got release startegy for five release codes i.e L1,L2,L3,L4 and L5 for purchase orders
    Release startegy is based on Pur order category,doctype, Net order value and Pur group.
    For L1-L5 authorisation(all authorisations) is given for General managers.
    Currently when emergency is there general Manager has to release L1 to L5 all release codes.
    Requirement is that instead of releasing all can it be possible to release only L5 so that all can be released.( This authorisation is for only for L5)
    Once the authorisation is there for all any customisation possible for releasing code L5 so that remaining all release codes can be released.
    Please suggest.
    Regards,
    Dayanand

    Hi Mr.Shawn,
    I have removed ticks for L1,L2,L3,L4 in Release prerequisites then release startegy L1 L2 L3 L4 kept as Released.
    Then Even if release one all releasing.
    But Requirement is that when only L5 is released only All shall be removed, other wise remaining Releases shall be based on the old procedure only. L1 to L4 shall be L1 is released then only L2 can be released principle. But in case of L5 releases all shall be released.
    Is it possible, what needs to be done ,please suggest.
    Regards,
    Dayanand

  • Reg Release startegy, Class n characeristics

    Hi
    This is regarding PO release strartegy
    I setup Release strategy for PO's in Development system, for each release startegy allowed characteristic values are mentioned during config as expected
    I released transport to quality [we have 2 systems
    1. In One quality system i forgot to maintain classes, i maintained class, but still i am getting error 'Error in classification (class 032 class type 032)'
    2. in another quality system class and characteristics are maintained before releasing transport. when i see SPRO, system hasn’t assigned allowed characteristics values for each release startegy?  why?
    Do i need to perform any thing else other than creating characteristics and classes?
    What task should i b doing in target system
    Thanks in advance

    Thank you
    i understood exept 'donot open the client in quality and assign the values' what does this mean ?
    I am doing CL20N in quality only ?
    i understood in Qulity[target sytem]i must perform below
    --> create characteristics
    --> create class and assign characteristics
    --->CL20N assign allowed characteristic values for each release startegy

  • Difrence between work flow n release startegy

    hii frnds
    can anybody tell me wats the difrence between work flow n release startegy ..
    thnks
    rohit

    Workflow could be generic and can be configured for any process you want.
    When you want to control the releases of the documents depending on the parameters that you want to configure, you use the release strategies. While configuring release strategies, you can develop some workflows.
    Release strategies is more of a functional concept and workflow is the technical implementation.
    Regards,
    Ravi

  • Common issue SharePoint Admins faces daily

    common issue SharePoint Admins faces daily

    This is a common issue SharePoin Admins facing every other day. Even I have gone through this kind of situation where USP Sychronization Service was stuck in 'Stopping' state for 3 days.
    You must bring this service to 'stopped' state to make it normal again.
    Simply reset IIS on your SharePoint Application Server.
    Open Commad Prompt and type C:\iisreset
    Please remember to click 'Mark as Answer' and Vote as Helpful if the reply answers your query.

  • Common issues in data load monitoring...

    Hi all,
    Can u please tell me what are the common issues that occur during data load monitoring and how to rectify them??

    This is a bit dependent on your system and landscape. but to mention some of issues:
    - Deadlock in cube because the inxedes were not dropped before loading data into cube
    - Unallowed signs in master data prevent system from creating SID
    - Duplicate values in master data load (can be avoided by setting a flag in DTP)
    - Loading delta package without having intitialized before
    - Source package delivers key figure without units (this happens when laoding into a cube or an DSO with SID generation)
    - Missing replication of data source after transporting data source in source system
    Regards
    Aban

Maybe you are looking for