Data inconsistency in release procedure

Dear All,
I have one query regrading data inconsistency it is as follows.
I deleted one release strategy in development system and transported the same to Quality system.After transporting to Quality system I found some inconsistency in data in Quality system.
So now if I create deleted release strategy again in Development system and if I transport the same to quality will this get updated in all the tables as it was earlier(before transporting the deleted release strategy to quality).
Please help me.
Thanks in advance,
With Rgds,
Babu

will this get updated in all the tables as it was earlier
Pretty much Yes, it will have a different version though
Regards
Juan

Similar Messages

PR release procedure no longer working-error MEPO 822

I've raised a message previously regarding PR release problem. Now i've found something that need expert helps to clarify on this.
Situation :
One of my client(ABC) implemented release procedure for PR which is not assign to value limit. It is by document type. They had 2 document types; NB and RNB.
NB = NOT subject to release
RNB = SUBJECT to release.
So when they :
create a PR with document type RNB - it will goes for approval.
create a PR with document type NB - it will not go to approval.
It was working fine until after they created a new document type which copied from NB, called ZTP.
ZTP = NOT subject to release.
They did not touch anything on PR release configuration. However, the release has no longer working. Means, when they create PR with document type RNB, it will NOT go for approval as it suppose to. I've check in configuration, all are fine.
Findings:
I've created a PR, and go to ME45N to release it but system prompt me an error message
"Purchase requisition 10000066 cannot be released". I check on the message data, the error coming from MEPO, message number 822.
So i check in OSS and found a note which is similar to this case.
Note 939371 - Overall release PR using ME54N gives error MEPO 822
Link : https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=939371#Text
But my question is,is it also applied to ME51N and without external application as per my client's case?
Please anyone help.
Thanks.

Hi guys!
Wants to share something. I had a problem to release my PR. When i want to release PR via ME54N, system give me error message "Purchase requisition 10000066 cannot be released". When i checked message data, it is coming from MEPO Messafe 822. So i asked SAP, they said this one is caused by different issue. Here's the reply from SAP.
Here's the reply from SAP :
Purchase requisition 10000066 cannot be released
Message no. MEPO822
Now click the other requisition button and let say
choose Purchase requisition 10000068,
Execute ME54N again:
Purchase requisition 10000068 cannot be released
Message no. MEPO822
Comment/explanation:
The log incidence seems not having problem with release
strategy as it was ok but it was the last PR was called
everytime ME54N was called. This same as it works in enjoy
transaction ME21N/ME22N or ME51N/ME52N.
For example, When using ME21n or ME22n to create or change PO,
after saving the PO. There are 2 ways to exit the transaction,
1, enter another T-code or use /n to exit directly.
2, use 'F3' or the 'green tick' to exit ME21n (or ME22n)
Then you can access ME23n to see the difference.
For the 1st way, ME23n won't display the last PO created in ME21n
For the 2nd way, ME23n will display the last PO just created!!!
Please see attached consulting note 595627 that explains a new
functionality as of release 470:
Due to performance problem, a decision had to be taken about the way to
use transactions. If you leave transaction ME21N/ME22N via the
exit button (F3), the expected PO will be displayed next time you use
these transactions. But if you quit abruptly (/nXXX) the PO number
won't be saved for the next transaction ME2?N.
As SAP note is the official document to explain system behavior,
this document is provided by SAP developement to explain this system
behavior to customers.
In your case, you had used ME54N and this was same as you use ME53N.
The last PO always display. You may try to view Purchase requisition
with release strategy, for example Release group R1, Rel. strategy
R1, then after this execute transaction ME54N again, the message
MEPO822 will not be there anymore.
Hope this will help you guys if you're having the same problem in future.
Thanks,
Crystal.

Data inconsistency: posting with restricted transaction type (FAA_POST047)

Hi colleagues!
I have the following error:
Data inconsistency: posting with restricted transaction type
Message no. FAA_POST047
Diagnosis
You are trying to post in company code 1000 with transaction type 130 in ledger group 0N. According to table TABWA, this transaction type is limited. Nonetheless, according to your entries, you want to post to area 11.
System Response
Using limited transaction types is obsolete and would lead to an inconsistent posting in this situation. The system rejects the posting.
Procedure
Use a transaction type that is not limited. And, if possible, choose the ledger group and/or depreciation area on the initial screen.
According to specific accounting we shouldn't post to one of the depr. area, so most of the tr.types are restricted to post to all areas except this one.
Because of this, posting from MM with acc.assignment 'A' is impossible - I have this error.
Any ideas how to solve?
Thanks in advance

Hi Anton
This looks like your transaction type -130 is limited to post only in ledger group-0N as per the transaction type configuration. Due to which system is unable to post all the ledgers and hence this lead to inconsistency.
Please verify the transaction type 130- in configuration T code - OAYA and see if it is restricted by depreciation area (eventually allow to post only ledger group- 0N.
Tcode - OAYA (Limit Transaction Types to Depreciation Areas)
please verify and let us know the update. hope this helps
Best Regards
Jomon

Release procedure problem and error

Dear Friends ,
I facing some major problems in release procedure , i had configured one release procedure in 4levels , due to some reason i had deleted 3release groups and codes due to it was not working . But after deleteing in purchase order it showing all release level and only firest level is working unable to make MIGO and other release levels are not working . The relese code which i had created is appearing in RFQ/CONTRACT etc automatically . I had not created for this any release level . It's very very different case ....till date never faced and heared . How to resolve this probelm . Due to what reasons this kind of problems occurs .
RB

Hi,
Try to delete all the release procedure available in the system.
First try to do the documents coorectly and configure.
You might have done mistake in assigning the charcteristics to the class
Please try create a NEw release procedure once again.
Don't worry about the procedure in the RFQetc...
G.Ganesh Kumar

With classification release procedure for PO

Dear Experts ,
here one issue is with classification release procedure for PO
when I create characteristics
in Additional data
table name :-- Cekko field name :-- match code
enter
click all sec charars then which block I select to go next screen
and fill name is right or ?
please help me

hi,
in additional data field you have to give the field name of characteristic you are maintaining. like if you want to maintain characteristic as document type of the PO then we have to give the field name for document type mentioned in table CEKKO i.e. BSART.
then you have to do the value assignment. here you have to tick the check box for "NOT READY FOR INPUT".
JASH

How to configure release procedure for rate contracts release

Dear all,
How to configure release procedure for rate contract following are the requirements
they are two release codes c1 & c2 <=100000,>=100000
                if c1 is not there c2 has to be approved
     Change in the value of the rate contract contract
     Change in the validity of the rate contract
     Addition of deletion of line items
While using a non u2013 released rate contract in the PO an error message should shoot out.
Also the logic should be changed while using the rate contract in the PO.
The usage of the rate contract should be till the validity of the rate contract. i.e. the measurement should be end date of the rate contract and the PO creation date and not the delivery date of the PO. &
It should be possible to refer existing valid rate contracts in purchase orders.
Regards,
bhaskar

Hi,
In SAP rate contract is known as value contract denoted with wk. The release procedure for rate contract is same as that of other contracts and scheduling agreements. The tables for contracts will vary with SA (Scheduling agreement) .You may try and maintain condition records based on the customer combination and maintian the validity date of condition records as per your requirement.For contract and PO will have the same header/item table as EKKO/EKPO, and the release
class in standard is the same FRG_EKKO, you can use the same for contract.
To distinguish if it's a contract or PO, EKKO-BSART can be used.
For contract EKKO-BSART will be MK or WK, while PO will have NB/UB etc..
You can restrict the document type to set up the release strategy for only contract.
Of cause, you can also create your own release class Z* for contract copying standard
one FRG_EKKO via CL01/Class type 032, and then assign the class Z* to customizing:
OLME:
-> contract
->Release Procedure for Contracts
->Define Release Procedure for Contracts
->Release Groups
If you have already created the PO release class.
Assign a new chracteristic of Document Category -BSTYP
Please check below link for detailed release procedure. I hope this wil help you out .Thanking you.
http://wiki.sdn.sap.com/wiki/display/ERPSCM/RELEASE+PROCEDURE#RELEASEPROCEDURE-TABLESUSEDFORRELEASEPROCEDURES

Purchase Requisition Release Procedure Modification

Hi
In Purchase Requisition Release, we have two deviations in business requirement from standard SAP behaviour:
1. In multistep release, system allows PR release to be revoked by a lower level release authorized person even though higher level release has been done. Example, PR Release has release codes A1, A2 and A3, A2 can revoke release even after A3 has released the same. How do I prevent this from happening?
2. If business requirement is to have release procedure based on item cost per unit and not on total value of the line item, how can this be achieved?
Appreciate any guidance on these issues
Thanks
Sriram

Hi,
There is BADI ME_REQ_POSTED
in method POSTED you can write your code to trigger the workflow and get the information related to release strategy and
Purchase requisation .
for more than one PR use below logic .
LOOP at im_eban into gwa_im_eban .
    concatenate gwa_im_eban-banfn gwa_im_eban-bnfpo into gwa_objkey .
add data into container -----------------
      gwa_event_container-element = 'PurchaseRequisition'.
    gwa_event_container-value = gwa_im_eban-banfn.
    append gwa_event_container to gi_event_container.
    clear: gwa_event_container.
    gwa_event_container-element = 'ItemOfRequisition'.
    gwa_event_container-value = gwa_im_eban-bnfpo.
    append gwa_event_container to gi_event_container.
get the other details and create event to start workflow .
select single * from eban into lwa_eban where banfn = gwa_im_eban-banfn
                                              and bnfpo = gwa_im_eban-bnfpo .
        if sy-subrc <> 0 .
      call function 'SWE_EVENT_CREATE'
        exporting
          objtype           = 'BUS2009'
          objkey            = gwa_objkey
          event             = 'zcreated'
        tables
          event_container   = gi_event_container
        exceptions
          objtype_not_found = 1
          others            = 2.
ENDLOOP .
Hope this will resolve your issue.
Thanks and Regards,
Deepanker Dwivedi

IDOC data inconsistency

Hi experts,
i have an issue that there is data inconsistency in IDOC( delivery address created with respect to PLANT instead of STORAGE LOCATION).
now i want to rectify the issue by checking the mapping in the program , the IDOC is created by standard procude ( thorough ME21N).
can anybody tell me how can i find the program/interface name where the logic is written for filed mapping for IDOC
IDOC type ORDERS05
Message type ORDERS
Thanks
Niru

Hi ,
I have put a breakpoint inside the FM IDOC_OUTPUT_ORDERS and try to reprocess the idoc from WE19, but the control not stoped at Break point .
assume below is validation inside the FM makng the issue.
IF pekko-werks NE space AND
      pekko-kunnr EQ space AND
      pekko-emlif EQ space AND
      pekko-adrn2 EQ space AND
      pekko-adrnr EQ space.
     CLEAR int_edidd.
     CLEAR e1edka1.
     int_edidd-segnam = 'E1EDKA1'.
     e1edka1-parvw = 'WE'.
*- if Third party order, send customer number of first S.O. item -----*
     PERFORM fill_kunnr_header.
     e1edka1-lifnr = pekko-werks.
     lv_prog = 'SAPLEINM'.
     PERFORM fill_e1edka1_we_gln IN PROGRAM (lv_prog) IF FOUND.
     PERFORM edka1_fuellen.
* Call Method PROCESS_IDOC_SEGMENT (BADI MM_EDI_ORDERS_OUT)
     PERFORM badi_process_idoc_segment.
* Call Customer Function 002 (enhancement MM06E001)
     PERFORM customer_function.
*   Außenhandelsdaten
*   Partnerzusatz für IMPINV01 ab Release 4.0A z.B. Zoll-ID-Nummer
     IF control_record_out-idoctp(6) EQ 'IMPINV'.
       PERFORM fill_e1edkaz.
     ENDIF.
   ENDIF.
*- Manuelle Anlieferungsanschrift, wenn in allen Positionen gleich ----
   IF pekko-adrnr NE space AND
      pekko-kunnr EQ space.
     CLEAR int_edidd.
     CLEAR e1edka1.
     int_edidd-segnam = 'E1EDKA1'.
can you please tell me how can control stoped at this code?
regards
niru

Release procedure with classification not getting triggered

Hi,
I have configured the new release procedure for the PR release of type with classification, but its not getting triggered. Earlier my SAP system had without classification in place, but I wanted to have with classification. Can any one suggest how do I switch between two.
Ideally once I create the release group in with classification procedure that procedure gets activated and gets triggered. Unfortunately its not happening in my case. I tried deleting the entries from the without classification side too, but still it doesnt respond. Is there in patch or note missing.
Your suggestion would be highly appreciated.
sachin

Hi Jurgen,
I am configuring it for PR and with classification method. Well for simplification I am using just purchase group as characteristics, but still its not working. Earlier system had without classification in place, as its there in a default system and used to get triggered. When I created new procedure its not getting triggered. To be assured I deleted the data from witout classification, but still its not working.
Where as I did the same setting for PO, its working and giving me correct releaes strategy.
My characteristic is PRGRP using the communication structure CEBAN and field as EKGRP
Please suggest me on this.
sahcin
Edited by: sachin sagane on May 18, 2010 6:32 PM

Purchase requisition release procedure through User-Exit

Hi Workflow Guru,
I have a requirement to configure purchase requisition workflow . the workflow should trigger through release strategy.
The approver should determine through user-exit and the approver should determine based on value and quantity and that can be define in user-exit. as per my knowledge the value should mantain in SPRO-Release procedure. Please clarify me is it possible through user-exit. I am worked on user-exit for release procedure based on purchasing group.
Thanks in advance.
Regards,
Ranjan Tiwari

Hi,
There is BADI ME_REQ_POSTED
in method POSTED you can write your code to trigger the workflow and get the information related to release strategy and
Purchase requisation .
for more than one PR use below logic .
LOOP at im_eban into gwa_im_eban .
    concatenate gwa_im_eban-banfn gwa_im_eban-bnfpo into gwa_objkey .
add data into container -----------------
      gwa_event_container-element = 'PurchaseRequisition'.
    gwa_event_container-value = gwa_im_eban-banfn.
    append gwa_event_container to gi_event_container.
    clear: gwa_event_container.
    gwa_event_container-element = 'ItemOfRequisition'.
    gwa_event_container-value = gwa_im_eban-bnfpo.
    append gwa_event_container to gi_event_container.
get the other details and create event to start workflow .
select single * from eban into lwa_eban where banfn = gwa_im_eban-banfn
                                              and bnfpo = gwa_im_eban-bnfpo .
        if sy-subrc <> 0 .
      call function 'SWE_EVENT_CREATE'
        exporting
          objtype           = 'BUS2009'
          objkey            = gwa_objkey
          event             = 'zcreated'
        tables
          event_container   = gi_event_container
        exceptions
          objtype_not_found = 1
          others            = 2.
ENDLOOP .
Hope this will resolve your issue.
Thanks and Regards,
Deepanker Dwivedi

Release Procedure

Hi,
I have create a Purchase order Over delivery tolerance 2% above create new Release Procedure.
Plz, advise me.
By,
Hari.S

Hi,
i have user exit used for trying but not worked. i have created step below.
User Exit for : M06E0004.
Used for Exit Code Enter:
DATA : wa_bekpo LIKE LINE OF it_bekpo.
MOVE-CORRESPONDING I_CEKKO TO E_CEKKO.
READ TABLE it_bekpo INTO wa_bekpo INDEX 1.
IF sy-subrc EQ 0.
E_CEKKO-USRN1 = wa_bekpo-UEBTO.
ENDIF.
and executed not worked.
plz, Advise Step by Step.

Release procedure for p.o.

hi sapgurus,
here is the scenario,
i have as issue ( for P.O value only)
1) if the value is < 2 lacks then one person will release.
2) if the value is > 2 lacks then 2 persons will release

hi,
3.4.24 Releasing Procedure for Purchase Documents
Use
This setting is incorporated to just give demonstration of how SAP Release procedure works. The aim of this procedure is to replace manual written authorization procedures using signatures by an electronic one, while maintaining the dual Ctrl principle. The person responsible processes the purchasing document in the system, thereby marking it with an "electronic signature" which can give the document legal force.
3.4.24.1 Creation of Characteristics
Procedure
1. Access the activity using one of the following navigation options:
IMG Menu Materials Management  Purchasing  Purchase Order  Release Procedure for Purchase Orders  Edit Characteristic
Transaction Code CT04
2. On the Characteristic screen, make the following entries.
3. In put POVAL in filed Characteristic and choose Create (White paper) icon or Ctrl + F3 to begin creation of characteristic.
Field name Description User action and values Note
Select Addnl Data tab
Table Name Table Name CEKKO
Field Name Field Name GNETW
Choose Enter to continue, system will give an information message saying Format Data taken from ABAP dictionary, Choose Enter again to continue.
Select Basic Data tab
Description Description Total net order value
Status Status Released
Data Type Data type Currency format Selected by system
Number of characters Number of characters 15
Decimal places Decimal places 2
Currency Currency INR
Interval vals allowed Interval values allowed Check this tick box
Multiple Values Multiple values allowed Select this radio button
4. Choose Enter to complete the entries
5. Choose Save icon or Ctrl + S to save the characteristic.
3.4.24.2 Creation of Class
Procedure
1. Access the activity using one of the following navigation options:
IMG Menu Materials Management  Purchasing  Purchase Order  Release Procedure for Purchase Orders  Edit Class
Transaction Code CL02
2. On the Class screen, make the following entries:
Field name Description User action and values Note
Class Class PORELPROC
Class Type Class Type 032
Choose Create icon or white paper icon to create new class.
Description Description Purchase Order Release Procedure
Status Status Released
Choose Char. Tab to input characteristic name.
Characteristic Characteristic POVAL Created in above step
3. Choose Enter to complete the entries
4. Choose Save icon or Ctrl + S to save the characteristic.
Result
Class type 032: Class PORELPROC created.
3.4.24.3 Configuration of Release Procedure
Procedure
1. Access the activity using one of the following navigation options:
IMG Menu Materials Management  Purchasing  Purchase Order  Release Procedure for Purchase Orders  Define Release Procedure for Purchase Orders
Transaction Code SPRO
2. On executing the transaction system will give a popup screen choose Release Groups, system will display Change View u201CRelease Groups: External Purchasing Documentu201D: Overview.
3. Choose New Entries icon and make the following entries:
Field name Description User action and values Note
Rel. Group Release Group 02
Class Class Name PORELPROC Created in above step
Description Description PO Release Procedure
4. Choose Enter to complete the entries
5. Choose Save icon or Ctrl + S to save the entries.
6. Choose yellow arrow to go back to popup screen.
7. Choose Release Codes to select.
8. Choose New Entries icon and make the following entries:
Field name Description User action and values Note
Grp Release group 02 Created in above step
Code Release Code 01
Workflow Workflow Leave it blank
Description Description Purchase Officer
Grp Release group 02 Created in above step
Code Release Code 02
Workflow Workflow Leave it blank
Description Description Materials Manager
9. Choose Enter to complete the entries
10. Choose Save icon or Ctrl + S to save the entries.
11. Choose yellow arrow to go back to popup screen.
12. Choose Release indicator to select.
13. Choose New Entries icon and make the following entries:
Field name Description User action and values Note
Release ind. Release Indicator 1
Released Released Leave it blank
Chgable Changeability 4
Value change % Change of value 10%
Description Description Purchase Order Blocked
Go to 2nd line and input the following values:
Release ind. Release Indicator 2
Released Released Select Check box
Changeable Changeability 6
Description Description Purchase Order Released
14. Choose Enter to complete the entries
15. Choose Save icon or Ctrl + S to save the entries.
16. Choose yellow arrow to go back to popup screen.
17. Choose Release Strategies to select.
18. Choose New Entries icon and make the following entries:
19. System will give new screen New Entries: Details of Added Entries
Field name Description User action and values Note
Release Group Release group 02
Rel. Stategy Release Strategy S1
Capital Items Release
Release Code Release Code 1 01
Release Code Release Code 2 02
20. Choose Enter to complete the entries.
21. Choose Release prerequisites icon and select check box 02 at the bottom and choose Enter.
22. Choose Release statuses icon, system will give a popup screen system will default 1, 1 and 2 entries one by one as a default. Choose Continue.
23. Choose Classification icon, here you can see Total net order value is displayed, please input >= 1.00 INR value in the white placed and choose Enter.
24. Choose Next Screen icon or choose F8 to continue.
25. If you want to simulate the release procedure you can choose Release Simulation icon.
26. Choose Enter to complete the entries.
27. To save the settings choose Save icon or Ctrl + S.
Result
Release procedure is saved.
3.4.24.4 Assignment of Values to Release Procedure
As a default all the purchase documents >= Rs. 1000000.00 is suggested in the following step of release procedure, if you want to have different one you need to change the value in the following step. If you do not want release procedure you may change the value to Zero.
Procedure
1. Access the activity using one of the following navigation options:
IMG Menu Cross-Application Components  Classification System  Assignments  Assign Object to Classes
Transaction Code CL20N
2. On the Class screen, make the following entries:
Field name Description User action and values Note
Class Type Class Type 032
Choose Enter to Assign values.
Release group Release Group 02
Rel. Strategy Release strategy S1
Choose Enter.
System will give Class name in Assignments, Double choose Class Name.
System will display Characteristic name Total net order value. Assign the value >= 1000000.00 INR against filed Value.
3. Choose Enter to complete the entries
4. Choose Save icon or Ctrl + S to save the characteristic.
Follow these steps
G.Ganesh Kumar

BDC/LSMW for SPRO to MM to Purchasing to PR to Release Procedure to ...

Hi experts,
May I know those screen in SPRO can do BDC or LSMW? I am facing problem on trying up the BDC using SM35 on the following screen. (I can't get the transaction code).
The path is:
SPRO -> MM -> Purchasing -> PR -> Release Procedure -> Set up Procedure With Classification -> Release Strategies.. The SAP program is SAPL0ME2, but I can't execute it using SE38 since it's a program Type 'F'.
So may I know any possible way for us to use recording approach on these to do Mass insertion of data?
Thanks.
Cheers,
Wong
Edited by: Julius Bussche on Sep 12, 2008 10:37 AM

Hi Vijay,
First, you can try on SM30, V_T16FS. Simply double-click on 1 release strategy, then Click on "Classification". You will see the classification screen allow us to enter value on each characteristic of the class.
However, I try using SHDB (recording), it shows empty screen on the value for class in the 'Classification' screen.
Thanks.
Cheers,
Isaac.

Data inconsistency: Parallel depr. area is not posted - while doing F-90

Dear All,
While doing F-90 with transaction type 100 i am getting below error kidly suggest me if any thing is missing.
Error- Data inconsistency: Parallel depr. area is not posted
          Message no. AAPO104
Diagnosis
For chart of depreciation 1000, you defined this area (or these areas) as parallel depreciation areas for depreciation area 01. In the current transaction, however, not all of these areas are posted. This is not allowed.
Procedure
Check if the transaction type is limited to certain depreciation areas. If there is such a limitation, add the missing depreciation areas for the transaction type.
Check if the asset that is being posted manages all these depreciation areas.
Regards,
Sahil

Dear expert
    please read OSS note :Check note 67688
   210557 Mass retiremt w/ revenue in case of parallel crcies
124231 AAPO104 w/o reason in intercompany asset transfer
   97388 Asset transfer: Problems with parallel areas
Regards
   Ajeesh.s

Data inconsistency: Area 30 for value takeover is missing

Hi Experts,
I am trying to enter Asset Transaction: Asset Sale Without Customer (ABAON) but I am getting the error below:
Data inconsistency: Area 30 for value takeover is missing
Message no. AAPO105
Diagnosis
According to its formula, depreciation area 31 is defined for mandatory takeover of values from depreciation area 30. However, depreciation area 30 was not posted during the current transaction (chart of depreciation MY01). This is not allowed.
Procedure
Check the specifications for the current transaction type.
I have checked OAYZ configuration. Area 30 does not have a 'Deactivate' tick on it. What does the Deactivate tick mean? If I need to change and tick it, how do I so since it is grayed out?
I hope someone can help me out with this.
Thanks,
Josef

Hi Josef,
This might be due to new depreciation area addition recently, is it ?
For the message in AFBN,
Depreciation area that you entered in chart of depreciation cannot be processed, as this program can only process real depreciation areas and not derived areas.
If it is a derived depreciation area then this program not works.
Based on initial error message it appears 31 is deriving values from 30. You might have run AFBN for area 30. Please check what the parameters in area 30. Some time dep.area defined as derived can be a real dep.area if it is the differences derived value from other dep.areas.
In that case please check the link back where exactly the values should come and flow.
Regards

Data inconsistency in release procedure

Similar Messages

Maybe you are looking for