PR overall release data inconsistencies

Hi Guru,
can anyone advise if anyone experience data inconsistencies issues in EBAN table if PR overall release is implemented? would appreciate if you could share the SAP OSS note if you have. Thanks in advance

Hi,
i recall seeing on the web that there might be data inconsistencies in EBAN if we activate header release. But i could not find the link subsequently. However, when i do testing for overall release, it seems ok so far. Thanks for replying anyway

Similar Messages

10.1.2.0.2 App Server Release Date?

Folks,
Does anyone know what the expected release date is for the Oracle 10g Application Server Release 2 Version 10.1.2.0.2 (Aka, the one with Forms and Reports services) and the accompanying 10.1.2.0.2 Developer Suite? I would like to get a feel so I can decide which one to load. 1 week? 1 month? 1 year?, etc. Thanks.
PJC

Well i badly need forms and report in my 10.1.2.0.0
When will it be release.
Expeting date please
RegardsWe waited for 9.0.4 to be released for way too long (about a year on the Windows platform). It is almost as stable as 9iAS R1 and it requires more resources (cpu and ram) to run but overall, it isn't too bad. We waited for 9.0.4 because it contained bug fixes we required to migrate from 1.0.2.2.2a. What does 10.1.2 have that 9.0.4.1 doesn't? I thought it was virtually the same thing as 9.0.4.1.

Overall release of PR in Release Strategy

I have created item-wise release of PR using with Classification of Rel Str.
But when I am creating overall release of PR I am not getting the tab.
I made settings in Rel Gp screen (ticked te check box for overall rel) & also ticked the check box in the document type of PR.
Pl guide
regards
VS

Hi VS
Am confused. You wrote 'Have created item-wise release strategy' and also asking 'Overall release'.
If you have "made settings in Rel Gp screen (ticked te check box for overall rel) & also ticked the check box in the document type of PR", then you have configured Overall release.
If PR does not get release strategy tab at header, it could be due to incomplete release strategies. No release strategy might have been triggered for your PR data. Do you see release strategy tab at item level ?
Best regards
Ramki

Release dates in PR

Hi Everyone
Can some one give me a detailed explaination on how the release date in calculated in a Purchase Requisition. I know that the Release date depends on the Planned Delivery time, GR processing time, Purchasing department processing time.
I want to know the diffference in the calculation of the Delivery date and the Release date in the Purchase Requisition.
Say for example in a PR for 'X' material
The Planned Delivery time for this material is 15 Days
The GR processing time is 5 Days and
The Purchasing Department Processing time is 5 Days
Now the system proposed the
 Request date as 11.10.07
 Release Date as 11.10.07
 Delivery Date as 02.11.07
For another material 'Y' with
Planned Delivery time - 45 Days
GR processing time is 5 Days and
Purchasing Department Processing time is 5 Days
Now for this material
The system proposed
Request Date as 11.10.07
Release Date as 12.10.07
Delivery Date as 3.12.07
Can some one explain why there is a difference in the Release dates
Points will be rewarded
Thank you
kavitha

Hi Kavitha
pls confirm whether PR is released through indivisual release or overall release
as in indivisual release u can release PR line items indivusualy e.g if pr contains two line items u can release one by one line items and release date is captured after that
Release date is nothing but that on which date line item is released( In case of PR )and calculated as Release date=requirement date -GR processing time- planned delivery time - purchasing department processing time.
Reward if usefull
Vishal....

Can't use Overall Release for Purchase Requisitions

I have two groups, AA and ZZ. Each group has it's own Class.
Group AA uses Cost Center Class (CN) (uses Characteristics Cost Center and Line Amount)
Group ZZ uses Order Class (OC) (uses Characteristic Order)
I have built one and only one Release Strategy for each of these Groups. These Strategies both work successfully when I select the other group to be the group for Overall Release. That is, if I set ZZ to be for Overall Release, then create a requisition, the release strategy for Group AA is applied successfully. However, if I modify the req the strategy for ZZ, does not get applied.
The opposite is true. When AA is set to be for Overall release, then ZZ works. However, if I modify the req, then AA's release strategy does not get applied.
Again, both strategies work correctly when the other Group is set to be the one to use for Overall Release. However, neither strategy works if its group is set to be the one for Overall Release.
What am I missing? I only have two classes, two groups, and two release strategies.

SAP Standard system allows only 8 levels of release codes.If client requirement is more than 8 then for excess release codes customisation is done by the technical team (Abapers).Lets take an example of 15 release levels required for a client according to his Business needs then in this case initial 7 codes are customised and remaining 8 release codes are configured in the system.
Release procedure is of two types
Release Procedure without classification
             This procedure is applicable only for Purchase Requisitions.
             Here PR is released Item by Item only.
Release Procedure with classification
            This procedure is applicable to PR,RFQ,Service Entry sheet,RFQ,PO,Contract and scheduling agreements.
            Item by Item and Header level releases can be configured
            For PR - both item by item and Header level release can be configured
            For external purchasing documents - Release is possible only at Header level.
Step 1:
Create Characteristics
In this step we need to create characteristics - conditions to be satisfied for triggering Release startegy.For example client has asked to set release strategy based on 3 inputs.Combination of value, Plant and Purchasing group
            1) Total value of PR more than Rs 50,000
               create characteristic as "Release_PR_total_value" in transaction code CT04.
              Tab - Basic data " Data type --- CURR currency format", "Decimal places - eg. 2 " and "currency eg. INR or USD"
              Tab -values key in > 50000 INR
              Tab - Additional Data- Table Name "CEBAN" and Field Name "GSWRT"
              Tab - Restrictions - class type - 032 - Release strategy
            2) Plant
                 Create characteristic "Release_PR_plant" in transaction code CT04.
                 Tab - Basic data - Data type - CHAR; Number of chars - 4
                 Tab - Values - Key in all the plants for which you are required to configure release proc. eg. 1000,2000,3000
                 Tab - Additional data - Table name CEBAN and Field Name is WERKS.
            3) Purchaisng Group
                 Create characteristic "Release_PR_PurchasingGroup" in TCode CT04
                Tab - Basic data - Data Type - char, Number of chars eg. 3
                Tab - values - Key in all the purchasing Groups for which Release proc. is to be configured as required by Client.
                Tab - Addnl Data - Table Name CEKKO and field name - EKGRP
Step 2:
Define class in transaction code CL02
Menu path SPRO>Materials Mgmt>Purchasing>Purchase Requisition>Release Procedure>Procedure with Classification>Edit classes
Here we assign all the above created Characteristics to a CLASS so that a release strategy to be triggered when all the conditions are met.
Create a new class with free choice of names as "PR_Release_proc" in transaction code CL02.*Key in the class name and select class type as 032 - RELEASE STRATEGY then click on symbol create to enter all the details as mentioned below.
Tab - Basic data - Enter description as "PR_Release-Proc",
status- Released, Same classification - check the push button - Warning Message
Tab- CHAR Enter above created 3 characteristics
1.Release_PR_total_value
2.Release_PR_plant
3.Release_PR_PurchasingGroup
step3:
Menu path is
SPRO>Materials Mgmt>Purchasing>Purchase Requisition>Release Procedure>Procedure with Classification>set up procedure with classification>
here define
1.Release Groups
Release group 01 is used for Purchase requisitions and 02 for Purchase orders.
Here assign class "PR_Release_proc" against release code "01"
check "OvRelPReq" indicator for over all release (All line items )of document in one shot else it will be released line item wise.
2.Release codes
Release codes are assigned to Release groups, in Workflow these release codes are tagged to users' SAP IDs through which they will be able to approve or reject a PR in SBWP(Inbox in SAP Business workplace.
PRs are released by users in transaction code ME54N.
Eg
Type of user            - Level -             Release code
PR creator - clerk or Business user -
Approver    - Supervisor                 -   R1
Approver -   Project Lead              -   R2
Approver   - Asst. Manager             - R3
Approver   - HOD/General Manager - R4
Release codes R1 to R5 are assigned to corresponding users.Manager R4 can only approve the PR if prior approvals till R3 are completed else not in ideal situation.
For detailed info please refer
http://help.sap.com/saphelp_erp60_sp/helpdata/en/75/ee1fa755c811d189900000e8322d00/frameset.htm
3. Release Indicator:
Release indicators show the release status of a Purchase Requisition.
For detailed info please refer SAP Help official site
http://help.sap.com/saphelp_erp60_sp/helpdata/en/75/ee1fa755c811d189900000e8322d00/frameset.htm
4.Release Pre requisites:
These define the order in which individuals or departments release the PR in sequence.
3.Release strategies
Create a new release startegy eg ."A1" or "U1" , write its description PR release for value >1 lakh
Now select release codes according to the Chart of Authority set by your client.
Eg.
Release startegy " A1 - PR release for value >1 lakh"
R1 - Supervisor
R2- Project Lead
R3- Asst. Manager
R4- General Manager
Now click on" Release Prerequisites "push button and check all the boxes in ascending order.Save the document
click on "Release statuses" push button, check release statuses then click on "Continue" push button.
In third push button you can maintain CLASSIFICATION data or later you can directly mainatain in transaction code CL20N for this strategy.
Classification data for example
1. Value - > 100000
2. Plant - 1000,2000,3000 etc
3. Purchasing groups - 101,102,103 etc
By clicking on "Release Simulation" push button you can check whether release is getting affected for configured release codes or not.
In this way you can configure all the required Release startegies.
Now create a PR in T code ME51N with the above conditions then a new tab will appear in PR creation screen at the time of check.Save the document and this can be released by respective users in TCode ME54N.
Tcode - ME54N - For Individual Release
Tcode - ME55 - For Collective Release
For detailed info please visit SAP HELP website
http://help.sap.com/saphelp_erp60_sp/helpdata/en/75/ee1fa755c811d189900000e8322d00/frameset.htm
http://help.sap.com/saphelp_erp60_sp/helpdata/en/75/ee1fa755c811d189900000e8322d00/frameset.htm
Regards,
Indranil

EIC- Data Inconsistencies in Productive System

Dear EIC Experts,
Have a query regarding data inconsistencies in the productive system. I will illustrate with an example,
An Activity was created and a follow up activity created on that and assigned to a resolver group.
There is an entry in SCMG_T_CASE_ATTR with Status 20 (Allocated)
and an entry in THREIC_ACTIVITY, with a whole load of data like creator org unit and owner org unit missing, all it has are the activity categories and the user id.
An entry exists in THREIC_FOLLOWUP with all relevant fields filled but Worlflow ID is blank. The status in this table is 40 (delivered).
So it looks as if no workflow was created and it did not go to anybody to action. And the activity cannot be closed and is just lying there, as the owner cannot take any action till the follow up status becomes completed.
1) What could be the possible reasons for this to happen? I have already checked that workflows are all activated and there are other activities being raised and clsoed just fine.
2) Is there anyway I can use any utility tools to correct the data in the back end in such a way that thia activity can be clsoed down?
I have a few hundred activities like these (from 30000 overall activities) which cannot be closed because of various data inconsistencies. Any ideas are appreciated.

Hi Harish
I have worked on multiple EIC implementations and I have never had this issue though the follow up functionality has been set up correctly and by the details in your email my guess is that it is not at your location.
It is possible to fix these 100 or so and set them to closed but it is to much to type out in this forum.
I would check out www.eicexperts.com as they are experts in EIC and they may walk you through it as they are very helpful.

PR overall release strategy

Hi
Greetings!
Overall all release strategy had already been set up in our system and it is working fine. But When i try to create a new strategy, it is not working.
We have a class for over all PR release with the following characteristics.
1) Purchasing Document type
2) Plant
3) PR total value
4) Cost center
5) Purchasing group
I have made the following settings which are relevant for overall release
1. Materials Management --> Purchasing > Purchase Requisition> Release Procedure --> Procedure with Classification --> Set Up Procedure with Classification --> Release Groups --> "Overall release of purchase requisitions" is checked for the release group created.
2. Materials Management --> Purchasing > Purchase Requisition> Define Document Types --> "Overall release of purchase requisitions" is checked for the PR document type.
Is ther any other settings which i am missing? Please help me in resolving the issue.
Gobinathan G

Hi Gobinathan G,
I am aware that you already did the following procedure:
1. Materials Management --> Purchasing > Purchase Requisition> Release Procedure --> Procedure with Classification --> Set Up Procedure with Classification --> Release Groups --> "Overall release of purchase requisitions" is checked for the release group created.
2. Materials Management --> Purchasing > Purchase Requisition> Define Document Types --> "Overall release of purchase requisitions" is checked for the PR document type.
However, since you are moving towards Overall release, what you must complete in order to achieve
the desired result, is to create a new Characteristic, and use it within the class parameter that
you already created to control the values in your release strategy. Then you have to associate the
new characteristic to the field name GFWRT in table CEBAN. It may be done in the Additional Data
Tabulator of the characteristic.
It worked for me.
Hope it helps.
Alfonso Chakarji

Purchase Requisition, overall release

Hi All,
I am using the overall release for my release groups. The releasing strategy depends on the cost center.
The releasing is workling fine so far, after I created a PR, the release tab appears in the header. BUT if I enter several items in one PR with different cost centers, the release tab does not appear. This also happens, if I enter 2 items with different cost centers in the PR and both of them are assigned to the same release strategy.
Are there any configuration in SAP to prevent this or do I have to use the itemwise release for that?
Thank you!

Use userexit
Enhancement : M06B0005
Component   : EXIT_SAPLEBND_004
CR : RDAK903063 SPOREDDY 04/05/07 changes to pick the release
              strategy if all the cost centers are same for all
                line items. Since the user Exit is activated the
                program is forcing the data to go through import and*
             field I_CEBAN-KOSTL is not blank the user exit is
                filling blank values to E_CEBAN during export.

My app on the app store is not on category lists sorted by "release date"

yesterday, i got an email from apple that my first app is now on the app store! when i submitted the iphone app (popr), i marked it as an arcade and action game, as well as falling under the category of "entertainment." my belief is that these chosen categories is where my app will be displayed in itunes (for example, since my game is marked under "entertainment," i believe that the app should be viewable by launching the app store, clicking "entertainment" as a category, and hitting the "release date" tab at the top).
i am wondering if my belief is correct - does anyone know whether my app will get on this "recently added" list within the next few days (or at all)?
thanks in advance!

Noon Sept 3 - his app
10 am Sept 3 - my app
9:55 am Sept 3 - her app
7:42 am Sept 3 - their app
6:55 pm Sept 2 - his other app
3:15 pm Sept 2 - my other app
7 am Sept 2 - their other app
5:10 pm Sept 1 - someone else's app
You seem to be under the impression that there is importance to being on the list above #25. While there can be benefit for a very short time, this is such a small factor in the overall success of your app that you should not put any planning or hope into it.
Your app is now down on that list and will never go higher. I'll repeat...it will only go lower, each time another new app is released. Forget about it.
You now need to market your app. Get it talked about on game forums, issue a press release via prMac and hope for good reviews.

Burndown by Project & Release dates

I have a scenario where we have multiple projects on the same team with the same team members and each project has a different release date. We would like to track the burndown for the work done per project and its release date to ensure we are on track
for the release. Also we need to know the overall individual team member capacity across the projects to identify if resources can be shared and thus they all have to be under the same Team. Is there a way to have multiple burndowns in Visual Studio Online?
We are using the Agile Project Management template. We previously achieved this by using pivot tables in Excel. But were hoping there is an easier way when using VSO so that we do not have to manage data separately in excel sheets.
Here's my scenario:
Sprint April
Project 1 under Team A. Release Date say April 10 - Burndown 1
Project 2 under Team A. Release Date say April 25 - Burndown 2
Project 3 under Team A. Release Date say May 15 - Burndown 3
What are my options here? Should I create multiple area paths and iteration paths? Have different team projects under the same collection? Please advise
Thanks
pooja dave

There are multiple ways to get something in this direction. The simplest would be to create 3 teams, one for each project, and put all the work for each team in its own Area. Your actual team (the people) can still use the root team (which can be configured
to show all the work) to plan their work across the different projects.
If you want to see the work on the burndown, you can then simply open the team dashboard for each individual team (work area/project) to see the status of the work in progress for each project.
You can also use the Team explorer integration into Excel to export all the data to a table that automatically updates when you hit refresh in Excel. That way you won't need to manage the data in 2 locations, just keep the data in TFS, and then use the Team
tab in excel to update your report.
Using different team project would also work, but makes it much harder for the team members to use the planning tools, there is no way in TFS to get a plan board or backlog view that goes across team projects.
My blog: blog.jessehouwing.nl

MSI Big Bang XPower II X79 release date

Whats the release date for this motherboard to the UNITED STATES?
MSI Big Bang XPower II X79 LGA 2011

We don't know, we have nothing to do with MSI marketing. We are MSI product users the same as you helping each other with problems and have nothing to do directly with MSI. You would need to ask MSI. Question like that my typical answer is that you will know the release date after you see it for sale in the stores.
>> How to contact MSI <<
http://us.msi.com/service/PreSaleForm/
As a matter of fact if we knew the release dates of products like that we would post it in the forum to avoid those kind of questions all of the time.

Why is it that when looking through new apps in the apps store on my ipad in release date mode does it return to the first 1-12 after viewing pparticular apps?

why is it that when I look through the new apps in the apps store in release date mode it returns to the first page after veiwing more information about some apps, I could be ten to twenty pages in and have it happen.
Also, I only speak and read English and although there are probably great apps for people from other nations, I don't want to wade through all the apps that I can't make use of. I expect that people of other nationalities or languages don't want to have to wade through every app that they can't make use of, is there not a way that alI users could filter by language?
I mean no offence to anyone but with a collection of hundreds of thousands of apps in all languages and the jump back to the begining after possibly being into the list by a number of pages I stop looking after awhile and I'm sure I've missed some excellent apps by doing so.

Contact iTunes support : http://www.apple.com/support/itunes/contact/

Standard report with po released date

hi mm experts,
request pl let me know is there any standard report which gives the po details and release indicator with released date of po.
pl help.
regards
Srihari

Hi
U can get Po release date per release code, use CDHDR and CDPOS tables in SE16
Enter transaction as ME28/ ME29N, Enter the range date,enter the object value as PO number (PO number should be 10 digit if the PO is not 10 digit, then add zero value for the prefix).
Then you can find the release date
Rest details u can find from ME2N report i.e Po details and Release indicator using dyanamic selection
Vishal...

Purchase Order released date field and table name

Hi,
Please tell me the Purchase Order released date field and table name.
Regards
Deepak

Hi,
Table : EKKO.
Fields : FRGKE,FRGZU.
You can get release date of PO from CDHDR table.
give object value as your po number and check.dont forget to give leading zeros.
The udate will be date field and transaction will be me29n for relaesed po.

PR Overall release issue

PR release strategy issue comes when Line items in PR added by two different persons, PR Release strategy(overall release) not getting triggered.
Release strategy is working fine if i create PR with only one user id.
Both id's maintained in classification.
Is this sap standard behavior??
Created PR 4201001933 line item 10. using User ID - 20061704
Triggered correct release strategy TD QH.
Added line item 20 using user Id - 345045 --- (release startegy gone)
classification Maintained for TD QH

We have a similar equirement since we have cost center as one of the characteristics in PR overall release strategy.
In our case we agreed with Business that the CC in the first PR line item will decide the release strategy. (Or the first CC of thefirst line item in case of multiple account assignment.) We wrote a small piece of code to achieve this, to enter that CC in ceban-kostl.
If your business requirement permits, you may follow this strategy, where user id of the first line item will derive release strategy.
Regards.
Satish Patankar.

PR overall release data inconsistencies

Similar Messages

Maybe you are looking for