Exact difference between Item category and Account assignment category

Can anyone plz give the exact difference between account assignment category and Item category
Thanks inadvance

Hi,
Account Assignment Category: Key indicating whether an item is to be assigned to an auxiliary account (such as a cost center). The account assignment category determines which account assignment data (e.g. cost center, account number, etc.) is required for the item.
Item category: Identifier indicating the characteristics of an item. The item category determines whether the following are necessary or allowed with regard to an item:
Material number, Additional account assignment, Inventory management in the R/3 System, Goods receipt, Invoice receipt.
Prase

Similar Messages

Item category and Account assignment category field grayed out in PR/PO

Hello all,
While making a PR/PO we use both the item category and account assignment category. However, after saving the PR/PO, when i try to change the fields through ME22N/ME52N, the fields are greyed out. I dont think this can be controlled through the layout screen.
Is there anyway the fields can be made modifiable in ME22N/ME52N ?
Please help!
regards,
Soumyadeep.

Hi,
Well, actually you can control the Field settings in customization of Document Type. Check the following :
Go to SPRO>MM>Purchasing>Purchase Order>Define screen layout at document level
Click on the desired Document Type and see if the Field selection for Item Cat and Acct Assignment is checked for Display for that Document Type. If it is then change it to Optional.
Now, Go to SPRO>MM>Purchasing>Purchase Order>Define Document Type and see if the Field Selection Key is assigned to the (Updated just now) document Screen layout.
Hope this helps,
Best regards
Amit Bakshi

Define G/L Account for Product Category and Account Assignment Category

Hello Experts,
I got a requirment to make a new entry in below SPRO path.
Define G/L Account for Product Category and Account Assignment Category
*Individual entries cannot be put into the change request*
*Message no. SV141*
*Diagnosis*
*For technical reasons, the entries cannot be fully specified in the change request. There are two possible reasons for this:*
*1. The key of an entry is longer than 120 characters. All entries whose keys match up to character 119, are then copied into the change request, rather than an individual entry.*
*2. The key of an entry contains fields of special data types, for example, packed numbers. The key can only be specified in the change request up to the first such field from the left.*
*all entries whose keys match up to character 26 are copied into the change request, rather than a single entry.*
*System Response*
*The selected entry is copied into the change request correctly, but other entries may be copied as well.*
My question is, If I make one entry and move to Quality and production system will it move only one entry or whole table will move?
Kindly help me.
Thanking you
Regards
Sharan

I got the same message trying to make an entry in SPRO:
Define Backend System for Product Category
I found the note 305942 describing exactly the issue for my and above mentioned entry, which offers the correction, then the note 326802 which offers the correction of the first notes. However, both notes are for Releases 4.6C and D (from 2000), and we are using EHP2 FOR SAP SRM 7.0.
I see another discussions in SCN regarding this topic, but haven't found real solution yet. Any hints? At least the answer to previous question from Sharan would be appreciated.
Best regards,
Toni

Defining G/L Account for product category and account assignment category

We are using the standard configuration to default in a G/L account for a given product category and account assignment category combination. This works well for us when it comes to the shopping transactions (i.e. BBPSC01, BBPSC02, etc.), however we have a problem with this logic in the carry out sourcing transction BBPSOCO01. Our users are creating describe requirements which are then delivered to BBPSOCO01, however the user is not assigning the correct product category, so the sourcing department updates the cart with the correct product category. Upon doing so, the G/L account gets changed to whatever the V_BBP_DET_ACCT table determines is correct for that given product category/account assignment combination. We would like to know if their is a way to not fire the "default G/L account determination" when the shopping cart is changed in transaction BBPSOCO01. I already know about the BBP_DETERMINE_ACCT BADI but thought there might be a less expensive alternative. Our business treats the G/L account provided by the configuration as a guideline, therefore when the buyer changes the product category they also want to retain the account assignment information. Any suggesstions on how this might be accomplished outside of creating my own logic in the BADI?
Best regards,
Shawn O'Connor

I got the same message trying to make an entry in SPRO:
Define Backend System for Product Category
I found the note 305942 describing exactly the issue for my and above mentioned entry, which offers the correction, then the note 326802 which offers the correction of the first notes. However, both notes are for Releases 4.6C and D (from 2000), and we are using EHP2 FOR SAP SRM 7.0.
I see another discussions in SCN regarding this topic, but haven't found real solution yet. Any hints? At least the answer to previous question from Sharan would be appreciated.
Best regards,
Toni

BAPI_PO_CREATE1 for blocked item and account assignment category Q

Hi,
I am facing an issue while creating PO with items which are blocked ie LOEKZ = 'S', and account assignment category 'Q'.
Though I fill wbs element in POACCOUNT and POACCOUNTX structures, after execution it is being erased and am getting an error: "Enter WBS Element" with an information message "Change G/L Account could not be effected".
Please help.
Thanks in advance.
Regards
Kalyani

Hi Ravi,
Below is the code:
POITEM-PO_ITEM = '00010'
POITEM-DELETE_IND = 'S'
POITEM-ACCTASSCAT = 'Q'
POACCOUNT-PO_ITEM = '00010'
POACCOUNT-SERIAL_NO = '01'
POACCOUNT-CO_AREA = '1000'
POACCOUNT-WBS_ELEMENT = 'XXXX'
I filled POITEMX, POACCOUNTX structures too.
When I dont pass POITEM-DELETE_IND = 'S', the PO is being created.
But my requirement is to make the item blocked.
Thanks in advance.
Regards
Kalyani

EXACT DIFFERENCE BETWEEN FULL LOAD AND REPAIRFULL LOAD?

HI Champ,
Can anyone explain me the exact difference between full load and Repairfull load?Give e some senario where we can go for this?Please.....
10zin

Hi,
Full repair can be said as a Full with selections. But the main use or advantage of Full repair load is that it wont affect delta loads in the system. If you load a full to a target with deltas running you again will have to initialize them for deltas to continue. But if you do full repair it wont affect deltas.
This is normally done we when we lose some data or there is data mismatch between source system and BW.
Check the OSS Note 739863 'Repairing data in BW' for all the details
Symptom
Some data is incorrect or missing in the PSA table or in the ODS object (Enterprise Data Warehouse layer).
There may be a number of reasons for this problem: Errors in the relevant application, errors in the user exit, errors in the DeltaQueue, handling errors in the customers posting procedure (for example, a change in the extract structure during production operation if the DeltaQueue was not yet empty; postings before the Delta Init was completed, and so on), extractor errors, unplanned system terminations in BW and in R/3, and so on.
Solution
Read this note in full BEFORE you start actions that may repair your data in BW. Contact SAP Support for help with troubleshooting before you start to repair data.
BW offers you the option of a full upload in the form of a repair request (as of BW 3.0B). If you want to use this function, we recommend that you use the ODS object layer.
Note that you should only use this procedure if you have a small number of incorrect or missing records. Otherwise, we always recommend a reinitialization (possibly after a previous selective deletion, followed by a restriction of the Delta-Init selection to exclude areas that were not changed in the meantime).
1. Repair request: Definition
If you flag a request as a repair request with full update as the update mode, it can be updated to all data targets, even if these already contain data from delta initialization runs for this DataSource/source system combination. This means that a repair request can be updated into all ODS objects at any time without a check being performed. The system supports loading by repair request into an ODS object without a check being performed for overlapping data or for the sequence of the requests. This action may therefore result in duplicate data and must thus be prepared very carefully.
The repair request (of the "Full Upload" type) can be loaded into the same ODS object in which the 'normal' delta requests run. You will find this request under the "Repair Request" option in the InfoPackage (Maintenance) menu.
2. Prerequisites for using the "Repair Request" function
2.1. Troubleshooting
Before you start the repair action, you should carry out a thorough analysis of the possible cause of the error to make sure that the error cannot recur when you execute the repair action. For example, if a key figure has already been updated incorrectly in the OLTP system, it will not change after a reload into BW. Use transaction RSA3 (Extractor Checker) in the source system for help with troubleshooting. Another possible source of the problem may be your user exit. To ensure that the user exit is correct, first load a user exit with a Probe-Full request into the PSA table and check whether the data is correct. If it is not correct: Search for the error in the exit user. If you do not find it, we recommend that you deactivate the user exit for testing purposes and request a new Full Upload. It If the data arrives correctly, it is highly probable that the error is indeed in the user exit.
We always recommend that you load the data into the PSA table in the first step and check the result there.
2.2. Analyze the effects on the downstream targets
Before you start the Repair request into the ODS object, make sure that the incorrect data records are selectively deleted from the ODS object. However, before you decide on selective deletion, you should read the Info Help for the "Selective Deletion" function, which you can access by pressing the extra button on the relevant dialog box. The activation queue and the ChangeLog remain unchanged during the selective deletion of the data from the ODS object, which means that the incorrect data is still in the change log afterwards. After the selective deletion, you therefore must not reconstruct the ODS object if it is reconstructed from the ChangeLog. (Reconstruction is usually from the PSA table but, if the data source is the ODS object itself, the ODS object is reconstructed from its ChangeLog). You MUST read the recommendations and warnings about this (press the "Info" button).
You MUST also take into account the fact that the delta for the downstream data targets is created from the changelog. If you perform selective deletion and then reload data into the deleted area, this may result in data inconsistencies in the downstream data targets.
If you only use MOVE and do not use ADD for updates in the ODS object, selective deletion may not be required in some cases (for example, if incorrect records only have to be changed, rather than deleted). In this case, the DataMart delta also remains intact.
2.3. Analysis of the selections
You must be very precise when you perform selective deletion: Some applications do not provide the option of selecting individual documents for the load process. Therefore, you must first ensure that you can load the same range of documents into BW as you would delete from the ODS object. This note provides some application-specific recommendations to help you "repair" the incorrect data records.
If you updated the data from the ODS object into the InfoCube, you can also delete it there using the "Selective deletion" function. However, if it is compressed at document level there and deletion is no longer possible, you must delete the InfoCube content and fill the data in the ODS object again after repair.
You can only perform this action after a thorough analysis of all effects of selective data deletion. We naturally recommend that you test this first in the test system.
The procedure generally applies for all SAP applications/extractors. The application determines the selections. For example, if you cannot use the document number for selection but you can select documents for an entire period, then you are forced to delete and then update documents for the entire period in the data target. Therefore, it is important to look first at the selections in the InfoPackage exactly before you delete data from the data target.
Some applications have additional special features:
Logistics cockpit: As preparation for the repair request, delete the SetUp table (if you have not already done so) and fill it selectively with concrete document numbers (or other possible groups of documents determined by the selection). Execute the Repair request.
Caution: You can currently use the transactions that fill SetUp tables with reconstruction data to select individual documents or entire ranges of documents (at present, it is not possible to select several individual documents if they are not numbered in sequence).
FI: The Repair request for the Full Upload is not required here. The following efficient alternatives are provided: In the FI area, you can select documents that must be reloaded into BW again, make a small change to them (for example, insert a period into the assignment text) and save them -> as a result, the document is placed in the delta queue again and the previously loaded document under the same number in the BW ODS object is overwritten. FI also has an option for sending the documents selectively from the OLTP system to the BW system using correction programs (see note 616331).
3. Repair request execution
How do you proceed if you want to load a repair request into the data target? Go to the maintenance screen of the InfoPackage (Scheduler), set the type of data upload to "Full", and select the "Scheduler" option in the menu -> Full Request Repair -> Flag request as repair request -> Confirm. Update the data into the PSA and then check that it is correct. If the data is correct, continue to update into the data targets."
Refer.
Repair full request
Re: Repair full request
Steps to perform repair full request
full repair request
repair full request
Re: Repair Full Request
Thanks,
JituK

Difference between Item Cost and Last Evaluated Price

Dear All,
What is the difference between Item Cost and Price in Last Evaluated Price List. Exactly when are they updated?
Regards
Sibasish

Hi Sibasish,
The "Last Evaluated Price" is simply a price list but can't have a direct manipulation like other price lists. Its values may not involve in any accounting transactions if it's not selected for the concerned transaction any way.
On the other hand the item cost is the cost which is maintained by SAP B1 (until and unless you select the Standard Valuation Method), and it gets involved in the accounting transactions where inventory is involved. For e.g. the "COGS" is calculated on the basis of this value.
Please close this thread if answered ... or please let us hear something more from you on this...

Wat is the exact differences between clustered table and pooled table

hi,
can you tell me ravi...wat is the exact differences between clustered table and pooled table
with regards//
anilreddyg

Hi Anil Reddy
Pooled Tables, Table Pools, Cluster Tables, and Table Clusters
These types of tables are not transparent in the sense that they are not legible or manageable directly using the underlying database system tools. They are managed from within the R/3 environment from the ABAP dictionary and also at runtime when they are loaded into application memory.Pool and cluster tables are logical tables. Physically, these logical tables are arranged as records of transparent tables. The pool and cluster tables are grouped together in other tables, which are of the transparent type. The tables that group together pool tables are known as table pools, or just pools; similarly, table clusters, or just
clusters, are the tables which group cluster tables.Not all operations that can be performed over transparent tables can be executed over pool or cluster tables.
For instance, you can manage these tables using Open SQL calls from ABAP, but not Native SQL.These tables are meant to be buffered and loaded in memory, because they are commonly used for storing internal control information and other types of data with no external (business) relevance. SAP recommends that tables of pool or cluster type be used exclusively for control information such as
program parameters, documentation, and so on. Transaction and application data should be stored in transparent tables.
Table Pools
From the point of view of the underlying DBMS as from the point of view of the ABAP dictionary, a table pool is a transparent table containing a group of pooled tables which, when created, were assigned to this table pool.
Field Type Description
TABNAME CHAR(10) Table name
VARKEY CHAR(n) Maximum key length n =< 110
DATALN INT2(5) Length of the VARDATA record returned
VARDATA RAW(m) Maximum length of the data varies according to DBMS
Table Clusters
Similarly to pooled tables, cluster tables are logical tables which, when created, are assigned to a table cluster. Therefore, a table cluster, or just cluster, groups together several tables of type clusters.Several logical rows from different cluster tables are brought together in a single physical record. The records
from the cluster tables assigned to a cluster are thus stored in a single common table in the database.A cluster contains a transparent cluster key which must be located at the start of the key of all logical cluster tables to be included in the cluster. As well, a cluster contains a long field (VARDATA), which contains the
data of the cluster tables for this key. If the data does not fit into a field, continuation records are created.
Field Type Description
CLKEY1 CHAR(*) First key fields
CLKEY2 CHAR(*) Second key field
CLKEYN CHAR(*) nth key field
PAGENO INT2(5) Number of the next page
TIMESTMP CHAR(14) Time stamp
PAGELG INT2(5) Length of the VARDATA record returned
VARDATA RAW(*) Maximum length of the data section; varies according to database system
Working with Tables
The dictionary includes many functions for working with tables. There are five basic operations you can perform on tables: display, create, delete, modify, copy. Please do not confuse displaying a table with displaying the table entries (table contents). In order to display a table, it must previously exist; otherwise the system will display an error message in the status bar. For the following example, the table TABNA is used. To display this table, from the main dictionary screen, enter the table name in the Object name
input field with the radio button selected next to Tables. Then, click on the Display button at the bottom of the screen, or press the F7 function key, or, alternatively,
select Dictionary object Display from the menu.
In this screen, you can see table information such as
¨ Table type, shown next to the name of the object. In the example, it is a transparent table.
¨ Short text description.
¨ Name of the user who made the last change, and the date of the change.
¨ Master language.
¨ Table status. On the screen, you can see this table is saved and active.
¨ Development class. For information on development classes, refer to Chap. 6.
Delivery class, which sets the maintenance group for the table. It controls how tables will behave during client copy procedures, upgrades, and so forth.¨
Tab. Maint. Allowed flag, which indicates whether you can generate a screen for maintaining table entries.
¨Then, on the lower part of the screen, you can see the table fields with all associated characteristics such as:
¨ Field name.
¨ Key indicator. When set, this field is the primary key, or part of it.
¨ Data element.
¨ Basic data type.
¨ Length.
¨ Check table.
¨ Short text, describing the field.
Additional information about the table can be displayed by selecting the corresponding functions from the menu or directly from the application toolbar, such as keys, indexes, or technical settings
Standard table:
The key access to a standard table uses a sequential search. The time required for an access is linearly dependent on the number of entries in the internal table.
You should usually access a standard table with index operations.
Sorted table:
The table is always stored internally sorted by its key. Key access to a sorted table can therefore use a binary search. If the key is not unique, the entry with the lowest index is accessed. The time required for an access is logarithmically dependent on the number of entries in the internal table.
Index accesses to sorted tables are also allowed. You should usually access a sorted table using its key.
Hash table:
The table is internally managed with a hash procedure. All the entries must have a unique key. The time required for a key access is constant, that is it does not depend on the number of entries in the internal table.
You cannot access a hash table with an index. Accesses must use generic key operations (SORT, LOOP, etc.).
Index table:
The table can be a standard table or a sorted table.
Index access is allowed to such an index table. Index tables can be used to define the type of generic parameters of a FORM (subroutine) or a function module.
Just have a look at these links:
http://help.sap.com/saphelp_nw04/helpdata/en/90/8d7304b1af11d194f600a0c929b3c3/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/74/83015785d811d295a800a0c929b3c3/frameset.htm
Regards
Sreeni

What's the difference between "Full Name" and "Account Name"

Just re-install a new OS X Lion. On the "Create Your Computer Account" screen, what's the difference between "Full Name" and "Account Name"?

Your computer name by default would be "John David Appleseed's Macbook Pro"
But you can always change that in System Preferences->Sharing
And yes, the first account you set up will be an administrator.

What is the exact difference between Purchse order and purchase requisition

Hi all,
What is the exact difference between Purchse order and purchase requisition.
Thx

Hi,
<b>Purchase Requisition</b>-> Staff in an orgn places Pur requisition for want of some goods/products - ME51
Related Table EBAN
Request for Quotation(RFQ)-> The Purchase dept in the orgn calls/requests for the quotation for the products against which PR was raised. - ME41
Vendor Evaluation->After receving the RFQ's, after comparison a Vendor is finalised based on the terms and conditions.
<b>Purchase Order(PO)</b>-> Pur order was issued to that vendor asking him to supply the goods/products -ME21N
Tables:EKKO,EKPO
Goods Receipt Note(GRN)->Vendor supplies the material/Products to the orgn-
MB01
Goods Issue (GI) -> People receives their respective itesm for which they have placed the Requisitions
Vendor, Material ,Qty are mandatory for PO.
Regards,
Padmam.

SC with combination of Limit and account assignment category as unknown(U)

Hi,
We are at SRM 5.5, Please let me know is it possible to create SC with combination of Limit and account assignment category as unknown(U) then PO with same combination and distrribution of cost to different cost centers at the time of confirmation from SRM side.
Please guide me processs of the same in steps
Many Thanks,
Venkat

It is for Extended Classic scenario

Exact difference between System status and the user status

Hi,
Please tell me the exact difference between System status and the user status .
how we customize the both in the system
Thanks & Regards
Prajith P
Moderation: Locked. Please, try to find an answer first. See rules of engagement
Edited by: Joaquin Fornas on Feb 23, 2012 11:14 AM

Hi,
As you mentioned there are 2 status can be maintained for documents like Equipment Master, Notification, Maintenance Order & other important business documents.
In case, client feels that system status is not enough to capture the details of the object, then user status can be used.
System statuses will be updated automatically based on business transactions which will be done on SAP.
For example, once the equipment is created, System status would CRTD (Created). If you install the same to some superior equipment or FL, then status would be INST (Installed).
If you keeping that equipment in Spare, then for that, you have to maintain separate User Status like AVLB (Available in Stock / Spare) so that through IH08, by using User status, you can the report which is available as spare.
These user status as per the name, should be updated by the user manually.
Regards,
Maheswaran.

What is the exact difference between Database Cloning and Database Refresh?

Hi,
Can anybody tel me the exact difference between Database Cloning and Database Refresh?
I Have some conflicts in these topics.
Thanks
Rajesh

Refresh is what it says, "refresh" . You have a main site which would always have the data being inserted into it. There would be another site which would remain some where else . This site needs to be refreshed with the primary site. So you need to do export from the primary, push it to the secondary site and done!
HTH
Aman....

Purchase order and Account assignement category- Change

hi.,
We are trying to receive the Purchase order of High value components into INVENTORY.
However, most of these Purchase Orders were created with account assignments.
Because of that, if we receives these POs, they will be consumed against the object identified in the account assignment.
Additionally, some of these have been invoiced already and would need to be backed out from the finance side.
Question: How can we receive these STO Purchase orders and then make changes through Movement type ( or any other way ) so that the HIgh Value Components that are consumed against that AC assignment can be subsequently moved into Invenotory.
Also, what are the other options ( FI will not open Previous period) so that the PO's which have been invoiced can be reversed against that AC assignment.
Thanks All

hi Rajesh.,
As mentioned earlier, these Purchase orders are STO's which have been already created and we are waiting to do the GR for the same. Items in the STO PO are of High value which we need to bring into INVENTORY.
But, because these STO PO's were created with account assignments, if we do GR now, they will be consumed against the object identified in the account assignment.
Some of these STO PO's have been invoiced already and FI has indicated that they could cancel the invoices for those STO PO's in previous posting period.
Question again : How can we receive these STO Purchase orders and then make changes through Movement type ( or any other way ) so that the HIgh Value Components that are consumed against that AC assignment can be subsequently moved into Inventory and not to a cost Center (202)
Step (1) Can we cancel the Invoiced items> reverse the GR for invoiced Items>reverse STO for PO ?
Step (2) Can we reverse the STO for PO for which GR has not been done? then
Step (3) Change the PO through ME22N, remove the Account assignment category?
Or how do we correct this situation for
(1) PO's already invoiced.
(2) PO for which GR has not been made. How can we receive them into Stock and not Cost center.
Anticipating a reply
Thanks
Sri

Item categiry and account assignment

Hi all,
Hav we create any item categiries and account assignments.
if yes,what business process required
please clarify
siri

HI,
Item Categories are std. one. I guess we cant create new ones.
But you can create your own account assignment categories using OME9 transaction.
Also assign the new account assignment category to Std. Item Categories before carrying out a transaction.
Thanks & Regards,

Exact difference between Item category and Account assignment category

Similar Messages

Maybe you are looking for