P.O - DIFF. BETWEEN INDIVIDUAL RELEASE & COLLECTIVE RELEASE

Dear All ,
Kindly explain the difference individual release & collective release , as i m using ME29N to release here this P.O is to be released by 3 persons - execut. Mgr & G.M , what is scenario in Collective rel procedure
sap11

Hi
It is not possible to release all POs in one time through ME28.
Through by this Tcode you can view list of all unreleased POs under one released code then one by one you can release all POs.
In SAP, there is not any provision to release all POs in one time.
Vishal...

Similar Messages

Diff between 7.7 to latest obiee release

hi
how much is diff between 7.7 analytics to latest verison of obiee

Not sure what the last 'Siebel' release was but there as been a few since. I can think of at least Time Series functions (OBIEE 10.x : AGO and TODATE) and Essbase support (OBIEE 'Plus') , "Time Series" graph in 10.1.3.4.1 .
I would personally read the the release notes. BTW the latest is 10.1.3.4.1
Others will no-doubt chime in with some more.

Error in Collective release of Service entry sheets

Getting an error message at the collective release of entry sheets (ML85).
Error: Total value of entry sheet differs from Total value of account assignment.
However in the same transaction code individual release is possible.
Please suggest

Hi,
Go to the PO check the values used in the account assignment tab.
It sounds like the multiple account assignments do not add up to the value of the serveice entry sheets being posted and the system needs to know how to manage the extra.
This does not normally happen if you have used percentages instead of values in the multiple account assignment screen, because it can spread the extra automatically.
The reason that the indicidual release is working is because this has not pusshed it over that value and postinmg several SESs has pushed it over.
Steve B

Collective Release of PR

Hi,
We have situation like the following :
Collective release is being used for PRs. If a line is deleted from purchase requisition we are not able to use collective release, we can only use ME54N individual release.
Is it SAP standard ? If a requisition item is deleted, we have to release PR from ME54N not from ME55. Is this correct ?
Regards
Alper

Hi,
The collective release determines that the items in a purchase requisition are all released at
at the same time (rather than individually).
If there are some items which can't be released (may be they are deleted), the transaction ME55 can't be used - so you have to release using the individual release

Budget not checked in collective release of service entry sheets.

Hi,
A service purchase order created on FY2013 with real fund center and commitment item, budget was consumed but open commitment item does not carry forward to FY 2014.Now user created service entry sheet and collective release it with t.code ML85. where budget was zero for FY2014 but system does not check budget make negative entry. How it is possible ??
Regards,
Rabin.

Hi Eli,
My basic issue is no payment budget value should be exceed than commitment value, like MIGO,SES,MB01,ML85 and ML81N value should be check available budget before post document.so that budget should not be negative. This is the critical requirement of my client.
system: EA-PS, release 600,SP level 24. Budget with BCS
Please recommend, Is above note applicable?
Regards,
Rabin.

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

Certain PR is not showing in collective release ME55.

Dear Experts
My clients is experiencing one issue at the time of collective release of PR using T. Code ME55. Certain PR is not showing at the time of executing with giving required input Release group and release code, however if the execution is done by giving input Release group, release code and Purchase Requisition the same document is showing. can any one tell me the possible reason for the same. Why the PR is not displaying for release using release code and release group in ME55.
Below Investigation has been done.
1. For single line item single PR is created through PS route using T.Code CJ20N.
2. Account assignment for the PR is "Q" Project Make to Order.
3. Line item not deleted for the same PR.
4. Status showing as 03 In Release (In Status tab).
5. in "Quantities/Dates" tab Closed check box in not activated.
Regards
Sanjib Naik
Message was edited by: Sanjib Naik

Hi Dev,
By default system is taking "Sort Indicator 1" Sorting by Purchase requisition number & item. with the combination of Release Code & Release Group.
I have tried with giving input Release Code, Release Group & Purchase Requisition Number
10032658 & 10034951after executing the sysem is showing Only one PR Number i.e 10032658 with 2 line item.
Here system is showing duplicate entry for PR. 10032658 of the first line item and ignoring to display the 10034951 details.
Final conclusion is that, system is not showing last PR Number. Instead of that 2nd last PR is displaying with duplicate entry.Please see the screenshot.
1. PR Number : 10034951 Delivery date is 30.08.2014 (Which is not Showing in ME55).
1. PR Numebr: 10032658 Delivery date is 10.07.2015 (Which is showing in ME55)
Thanks & Regards,
Sanjib Naik

Ifference between change request and release request and transport request

what is the difference between change request and release request and transport request and customization request?

Please refer to this link :
http://help.sap.com/saphelp_nw2004s/helpdata/en/57/38e1824eb711d182bf0000e829fbfe/frameset.htm
Regards,
Praveen
Pl reward if helpful

Diff between elementary & collective serach help?

frends tell me diff between elementary & collective serach help?

1) Elementary search helps describe a search path. The elementary search help must define where the data of the hit list should be read from (selection method), how the exchange of values between the screen template and selection method is implemented (interface of the search help) and how the online input help should be defined (online behavior of the search help).
2) Collective search helps combine several elementary search helps. A collective search help thus can offer several alternative search paths.
3)An elementary search help defines the standard flow of an input help.
4) A collective search help combines several elementary search helps. The user can thus choose one of several alternative search paths with a collective search help.
5)A collective search help comprises several elementary search helps. It combines all the search paths that are meaningful for a field.
6)Both elementary search helps and other search helps can be included in a collective search help. If other collective search helps are contained in a collective search help, they are expanded to the level of the elementary search helps when the input help is called.
http://help.sap.com/saphelp_nw04/helpdata/en/cf/21ee38446011d189700000e8322d00/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/cf/21ee45446011d189700000e8322d00/content.htm
The elementary search help must define where the data of the hit list should be read from (selection method),how the exchange of values between the screen template and selection method is implemented.
A collective search help combines several elementary search helps. The user can thus choose one of several alternative search paths with a collective search help.
Elimentary search help is a single search help and you will not see any more TAB's in the search help you will see only one dialog screen or directly the data.
In the case of collective search help you will have collection of search helps in to one search help. Dialogs of each search will be available as one TAB in the search help for that field. You include search helps which are similar into one collective search and use that for your field.
sri

Collective release in PR

Hi all,
In collective release for PR,using ME55 T.code,its find that check box is not enabled.. i check all the customization it correct only,kindly give suggestion... (overall release is tick marked and release strategy settings also correct).I use scope of list as "F"(Collective release).
Thnks & Regards
SAP MM User

Regarding the collective release, the scope of list ALV grid was
developed in order to fulfill accessibility requirements.
It is no longer possible to select several purchase requisitions
and release them all together. This was done on purpose and the user
should release the documents without the checkbox selection. This is not
a bug but rather considered a limitation in the design.
Please also review the below mentioned SAP notes :
668940 ME55 : collective release does not work with ALV grid.
788520 ME55:When choosing release,cursor is always moved to top
453888 FAQ: Reporting in the purchasing
I hope the information I have provided has also been useful.

Hi gurus what is the diff between free & refresh

hi gurus what is the diff between free & refresh

Hii!
FREE f.
Effect
FREE f has the same effect as CLEAR f , namely that a Data object f is reset to the initial value corresponding to its type.
Unlike CLEAR, FREE also releases any resources taken up by the data object f. FREE can also release more resources than CLEAR for table work areas declared using the TABLES statement.
After FREE f, the data object f can be re-addressed at any time. The only condition is that you may need to re-allocate resources to the object.
Note
If f is an internal table with header line (where the name f in a sense has two meanings) the statement FREE f refers to the body of the table, and the statement CLEAR f refers to the header line.
REFRESH itab.
Effect
The internal table itab is reset to its initial state, i.e. all table entries are deleted.
Der Return Code SY-SUBRC is undefined.
Notes
The header entry of a table with a header line remains unchanged. It can be reset to its initial value using CLEAR.
FREE itab can be used to free up the memory allocated to the table.
Note
Performance:
The runtime required to reset an internal table depends on the amount of memory previously occupied by that table.
Resetting a small internal table takes around 15 msn (standard microseconds). Resetting a 200 KB table takes around 400 msn, and a 1 MB table, around 3000 msn.
If the internal table has an index or a hash table (because it was edited using INSERT, DELETE, SORT or COLLECT), the runtime increases slightly, since the index or hash table has to be released as well as the table itself.
Regards
Abhijeet

Diff Between USEREXITS and CUSTOMER EXITS?

Hi all,
What is the Diff Between USEREXITS and CUSTOMER EXITS.REgards,
Kishore.

Hi,
A point in an SAP program where a customer's own program can be called.
In contrast to customer exits, user exits allow developers to access and modify program components and data objects in the standard SAP System. On upgrade, each user exit must be checked to ensure that it conforms to the standard system.
There are the following types of user exit:
User exits that use INCLUDEs -
These are customer enhancements that are called directly in the program.
User exits that use tables -
These are used and managed using Customizing.
Customer Exit
SAP creates customer exits for specific programs, screens, and menus within standard applications. These exits do not contain any functionality. Instead, the customer exits act as hooks. You can hang your own add-on functionality onto these hooks.
If you want to enhance the functionality of your SAP System, you should take advantage of the exits available in standard applications. There are two main reasons why you should use exits rather than modifying SAP software yourself. Add-ons attached to exits have the advantage that:
· They do not affect standard SAP source code
When you add new functionality to your SAP System using SAPs exits, you do not alter the source code of standard SAP programs in any way. The code and screens you create are encapsulated as separate objects. These customer objects are linked to standard applications, but exist separately from SAPs standard software package.
· They do not affect software updates
When you add new functionality to your SAP System using SAPs exits, your objects (called customer objects) must adhere to strict naming conventions. When it comes time to upgrade a to a new software release, customer objects names ensure that they will not be affected by any changes or new additions to the standard software package.
Customer exits are not available for all programs and screens found in the SAP System. You can only use customer exits if they already exist in the SAP System. You find find more information about locating applications with pre-defined exits in Locating Applications that have Exits
User Exits:
User exits allow you to add additional functions to the SAP standard.
Programs with user exits contain subroutine calls at certain points in their syntax that are identified by the prefix USEREXIT. The actual user exits are located in an include that has been assigned to a module pool. This is where customers can include any changes (enhancements) that they want to make to the system. These includes are always processed during program flow.
Advantage: In principle, customers can modify anything they want that is found in the include (tables, structures, and so forth).
Disadvantage: SAP cannot check the individual enhancements themselves which often leads to errors in the enhancement process.
Thanks and Regards,
Bharat Kumar Reddy.V

In LSMW, what is diff between LSMW-BAPI and LSMW-IDOC

hello all
In LSMW, what is diff between LSMW-BAPI and LSMW-IDOC

Hi Swamy,
The differences between IDoc and BAPI are as follows:
IDOC
IDocs are text encoded documents with a rigid structure that are used to exchange data between R/3 and a foreign system.
Idocs are processed asynchronously and no information whatsoever is returned to the client.
The target system need not be always online. The IDOC would be created and would send the IDOC once the target system is available (tRFC concept). Hence supports guaranteed delivery.
With asynchronous links the sub-process on the client can be finished even if the communication line or the server is not available. In this case the message is stored in the database and the communication can be done later.
The disadvantage of asynchronous links is that the sub-process on the server cannot return information to the calling sub-process on the client. A special way for sending information back to the client is required. In addition, a special error handling mechanism is required to handle errors on the receiving side.
IDOCs may be more changeable from release to release.
IDOCs are poorly documented.
BAPI
BAPIs are a subset of the RFC-enabled function modules, especially designed as Application Programming Interface (API) to the SAP business object, or in other words: are function modules officially released by SAP to be called from external programs.
BAPIs are called synchronously and (usually) return information.
For BAPIs the client code needs to do the appropriate error handling.
Problems with synchronous links occur if the communication line or the server is temporarily not available. If this happens, the sub-process on the client cannot be finished (otherwise there would be data inconsistencies).
Synchronous links have the advantage that the sub-process on the server can return values to the sub-process on the client that has started the link.
BAPIs are not totally immune to upgrades.
BAPIs are reasonably well documented.
Reward points if useful.
Best Regards,
Sekhar

Diff between 4.6c to 4.7 abap

diff between 4.6c to 4.7 abap

Hi
the differences are with respect to customer master and the CIN
In 4.6 cc the partner function tab is not there in the customer master
that is in the customer maste there is no display of the prtner functions in the customer master
But in the 4.7EE the partner functions are displayed on the customer master xd01 r vd01
And again in the 4.6CC , in the Cin version the tax procedure is TAXINJ
is used which gets te value from the function ebased
and in 4.7 EE the Tax procedure is TAXINN which gets te value from teh Condition based
and also in the customer master the CIN tab is not there in the customer master in the 4.6cc which is there in the 4.7 EE
You can find the difference in release notes of each SAP version.
Here are the links.
http://help.sap.com/saphelp_47x200/helpdata/en/fc/e3003deddfae4de10000000a114084/frameset.htm
http://help.sap.com/saphelp_scm50/helpdata/en/28/b34c40cc538437e10000000a155106/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/43/68805bb88f297ee10000000a422035/frameset.htm
Please visit the following links:
http://service.sap.com/erp
http://solutionbrowser.erp.sap.fmpmedia.com/ (Functional prespective)
http://service.sap.com/instguides --> mySAP Business Suite Applications --> mySAP ERP --> mySAP ERP 2005 --> Upgrade
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/LOVC/LOVC.pdf
For Functionality Differences pls refer to the below site -
http://solutionbrowser.erp.sap.fmpmedia.com/
After opening the site, please select the Source Release Version which is 4.6 b Then Select the Target Release Version which is "mySAP ERP 2005" or ECC 6.0
Select the Solution Area like Financial, Human Capital Management, Sales....
Select module like MM, PP, SD, QM.....
Click on Search
Then it displays the Release Version and the Delta Functionality. which can be downloaded to a word document if required.
and also check the release notes of ECC 6.0 in service.sap.com.
Hope this helps you.
Regards,
Sree
Message was edited by:
sree ram

Main diff between call transaction and session method

hi frnds.
my friend went for an interview they asked her whts the diff between call tran adn session?
she told more thn one transaction we can call for an session she told itseems. but he told tht by cal tran also u cn call more thn one tran it seems... so please canu help me out regarding this question? how we hve to tell in interview?
in advance thanks....

Hi
Batch Input and CALL TRANSACTION are both data transfer methods. Batch Input usually are used to transfer large amount of data. For example you are implementing a new SAP project, and of course you will need some data transfer from legacy system to SAP system. If there is no standard batch input program, direct input program, you would need to write your own data transfer program and it is going to be batch input program. CALL TRANSACTION methods is real-time method, whenever you run the program CALL TRANSACTION can be triggered. CALL TRANSACTION is used especially for integration actions between two SAP systems or between different modules. Users sometimes wish to do something like that click a button or an item then SAP would inserts or changes data automatically. Here CALL TRANSACTION should be considered. You use CALL TRANSACTION and you do everything automatically, collect necessary data, call transaction and so do database update. If any error occurs, show the user them.
Batch Input
With the Batch Input method, an ABAP program reads the external data that is to be entered in the R/3 System and stores the data in a batch input session. The session records the actions that are required to transfer data into the system using normal SAP transactions.
When the program has generated the session, you can run the session to execute the SAP transactions in it. You can explicitly start and monitor a session with the batch input management function (by choosing System - Services - Batch Input), or have the session run in the background processing session.
It offers management of sessions, support for playing back and correcting sessions that contain errors, and detailed logging. Your program prepares the data and stores it in a batch input session. A session is a collection of transaction data for one or more transactions. Batch input sessions are maintained by the system in the batch input queue. You can process batch input sessions in the background processing system.
Your program must open a session in the queue before transferring data to it, and must close it again afterwards. All of these operations are performed by making function modules calls from the ABAP program.
The most important aspects of the session interface are:
Asynchronous processing
Transfer data for multiple transactions
Synchronous database update. During processing, no transaction is started until the previous transaction has been written to the database.
A batch input processing log is generated for each session
Sessions cannot be generated in parallel. The batch input program must not open a session until it has closed the preceding session.
CALL TRANSACTION
In the second method, your program uses the ABAP statement CALL TRANSACTION USING to run an SAP transaction. External data doesnt have to be deposited in a session for later processing. Instead, the entire batch input process takes place inline in your program. With CALL TRANSACTION USING, the system process the data more quickly than with batch input sessions. Unlike batch input sessions, CALL TRANSACTION USING does not automatically support interactive correction or logging functions.
Your program prepares the data and then calls the corresponding transaction that is then processed immediately.
The most important features of CALL TRANSACTION USING are:
Synchronous processing
Transfer of data from an individual transaction each time the statement CALL TRANSACTION USING is called
You can update the database both synchronously and asynchronously. The program specifies the update type.
Separate LUW (Logical Units of Work) for the transaction. The system executes a database commit immediately before and after the CALL TRANSACTION USING statement.
No batch input processing log

P.O - DIFF. BETWEEN INDIVIDUAL RELEASE & COLLECTIVE RELEASE

Similar Messages

Maybe you are looking for