ME21N, Account Assignment, to set G/L Accout field 'read only

Hi,
I am creating PO with reference to Purchase Requisition (using T-Code ME21N). The fields 'Cost Centre' and 'G/L Account' under Account Assignment Tab are needed to be rendered 'Read only'.
The 'Cost Centre' Field has been made Read Only using User Exit. I am not able to do the same for 'G/L Account' field. Please suggest a possible way to do the same. Field Exit is not working and i have experimented with lots of BADIs, but to no avail.
Thanks,
Ranjan

Hi Venu,
I have done as you have told. This is working fine while creating
PO with reference to Purchase Requisition, but the problem arises when we try to create PO by simply putting Account Assignment Category 'K' along with other relevant data.
The G/L Account field is in display mode, obviouly due to configuration i have done, and thus we are not able to put value in it. It is interesting to note that SAP is itself determining and displaying G/L account in this case.We are checking if this is the case with all test cases. If so then our problem can be considered solved.
Thanks,
Ranjan

Similar Messages

Me21n - account assign - is it possible to add field ?

me21n -> account assign - is it possible to add field ?
is there any standart exit ?
i know about the optin to add fields in my own screen
( MM06E005 ) .
i need it becouse i can't inforce ( display message )
the user to insert value in my own subscreen .

hi
I have the same requirement of adding a new field in account assignment. Please let me know if you are done with that or you have any infor regarding user-exit/BADI.
Thanks
Alok

How to set a extended attribute as read-only in runtime

Hi Team,
I would like to set a extended attribute as read-only in runtime based in a condition.
I tried with "Criterion" in a extended model definition, but if the condition is false the content field disappear.
Best regards

Hi Bruno,
About the first part of your problem : User with permission and user without permission.
To meet your needs I would have defined a Group named "WithPermission" and associated this group to a Member (user) "A"
While other users would not have been associated with this group.
When an user login I would have checked what groups that are associated with. If the group "WithPermission" was found I would have allowed the current login user to write "My Example". If the current login user was not associated to group name "WithPermission". The user would not have been able to edit the field.
I did a search in the metamodel object and I found nothing Method. Following my reading it seems that it is not possible. Read below.
In Sybase Guide "Customizing and Extending PowerDesigner" - CHAPTER 7: Scripting PowerDesigner you can read the following :
Manipulating the Repository By Script
PowerDesigner lets you access the Repository feature via scripting using the RepositoryConnection as BaseObject global property.
It allows you to retrieve the current repository connection, which is the object that manages the connection to the repository server and provides access to documents and objects stored under the repository.
The RepositoryConnection is equivalent to the root node in the Repository browser.
You can access the repository documents, but you cannot access the repository administration objects, like users, groups, configurations, branches, and list of locks. In addition, only the last version of a repository document is accessible using scripting.
As described by Dirk I think the only thing you can do is to make a check on a specific username. Unfortunately it will be "hard coded" in your program. Or If you can by vb script access the repository tables. You could resolve your problem by checking Group permission associated to each users logged in..

Set sharing on system to read only now computer wlll not boot up

set sharing on system to read only now computer wlll not boot up

Hello skiboat2,
Because the permissions have been changed, you will need to put them back to what they were before. One of the ways to do that is to reinstall your OS X to make sure that everything permission wise gets put back to what it needs to be to work properly. Based of to the operating system that you say you have, I have provided the steps for reinstalling Snow Leopard. When doing this, it does not overwrite your personal data; it only touches the operating system.
Mac OS X 10.6: Reinstalling Mac OS X
http://support.apple.com/kb/PH6606
Regards,
-Norm G.

Set Cell or Row to read only if certain condition is met

Greetings,
As the subject suggest, I need to set Cells or Rows to Read Only or "Gray out" If Certain attribute doesnt contain any value.
The requirement is to search for records of certain range and display it in the table. And the records will not be editable (read only) if certain attribute/field of the record is NULL. In another words that particular row will be gray-ed out.
Right now I am able to extract out the range of records out and display it in the table but I am not able to set the display of the records/ rows to read only. Do note only certain row needs to be set to row only depending on a particular attribute.
I was to code these in WDDOMODIFYVIEW()... anyone have any solution to this? Points will be given of course. ")

Please dont use the DOMODIFY method for such changes.
The Properties mapped to the context are designed for exactly this purpose.
Your context node should be extended with another attribute. Eg attr_y_Read_only.
The read_only or enabled attribute of field y would then be mapped to this attribute.
Depending on cell editor type it may be called enabled or read only.
You then set this new attribute to true or false appropriately for each element in the node.
This new attribute, although inside the node, need not be displayed as part of the table.
It is there to help control fields in the each element.
Regards
Phil.

ME21N : account assignment mandatory for bulk material

Dear guru.
For a raw material used as bulk in production with material type ROH and quantity/value updating I need that when I create purchase order the system send an error message that account assignment is mandatory.
I know that for an NLAG or UNBW material type the system send this message.
For internal reason I need to maintain material type ROH with quantity/value updating , do you know a solution , any exit , in order to solve my problem ?
Thanks for you help.

CONS SAP wrote:
Dear
> I need that this component in the bill of material must be managed with position type L and I donu2019t want to do consumption movements.
> I have verified that I can create a purchase order with account assignment for this material , I need only that the system send a message for these bulk materials.
> Thanks.
position type L means it is a inventory managed material.
why do want the material to be inventory managed and at the same time dont want to record consumption movements?

How to set a MessageTextInput to be Read Only for a specific row?

Hi,
In Benefits Self Service, particularly the Update Beneficiaries page, it lists all your eligible Beneficiaries including yourself. The table has the following columns displayed for each beneficiary: Beneficiary, Relationship, Social Security Number, Primary %, Contingent %, Clear. This is the page where you allocate the Primary % and the Contingent %. The Primary % and Contingent % are MessageText Input.
We have a requirement that we wouldn't want an employee to designate himself/herself as a beneficiary. However, the employee is being listed as a beneficiary along with all the other eligible beneficiaries. Oracle says it is an intended functionality to include the employee in the beneficiary. Is there a way thru Controller Object extension to set the Primary % and Contingent % as Read Only but only for the row corresponding to the employee to prevent the employee from accidentally allocating himself/herself as a beneficiary.
I know there is the SPEL functionality but this requires me to add a transient attribute to the View Object corresponding to that table. But everytime I make a change to the View Object either by adding a transient attribute or some other changes, I end up getting an error on the standard Relation attribute of that view object. The error is something like "Relation set attribute failed for View Object". I cannot get pass this error and I'm not sure what's causing this. I see other people in this forum have encountered the same problem when extending view objects but no specific solution was offered nor any clear explanation of the cause.
So I thought if there's any way this could be done thru Controller Object extension. If so, please let me know how. The challenge for me I think is finding the bean corresponding to those Message Text Input but only for a specific row in the table.
Thanks,
Ronaldo

Hi,
I also tried extending the View Object but without changing anything to the SQL so it is exactly the same as the standard view object but I still get the "Attribute set for Relation in view object BeneficiaryPeopleVO1 failed". Based from this, extending the view object whether any change has been made or not affects the standard transient Relation attribute.
Here is the standard XML definition of the View Object if anyone is curious
<ViewObject
Name="BeneficiaryPeopleVO"
BindingStyle="Oracle"
CustomQuery="true"
RowClass="oracle.apps.ben.selfservice.enrollment.server.BeneficiaryPeopleVORowImpl"
ComponentClass="oracle.apps.ben.selfservice.enrollment.server.BeneficiaryPeopleVOImpl"
MsgBundleClass="oracle.jbo.common.JboResourceBundle"
FetchMode="FETCH_AS_NEEDED"
FetchSize="10"
UseGlueCode="false" >
<SQLQuery><![CDATA[
SELECT pcr.person_id person_id,
pen.prtt_enrt_rslt_id prtt_enrt_rslt_id,
con.first_name ||' '||con.last_name || ' ' || con.suffix Beneficiary,
con.national_identifier Ssn,
sum(decode(pbn.prmry_cntngnt_cd,'PRIMY',pbn.pct_dsgd_num,0)) primary_pct,
sum(decode(pbn.prmry_cntngnt_cd,'CNTNGNT',pbn.pct_dsgd_num,0)) contingent_pct,
con.person_id bnf_person_id,
con.business_group_id,
pen.per_in_ler_id,
pbn.pl_bnf_id pl_bnf_id,
pbn.object_version_number object_version_number,
pbn.effective_start_date,
pcr.contact_type contact_type,
con.full_name beneficiary_full_name,
sum(decode(pbn.prmry_cntngnt_cd,'PRIMY',pbn.pct_dsgd_num,0)) Db_Primary_pct,
sum(decode(pbn.prmry_cntngnt_cd,'CNTNGNT',pbn.pct_dsgd_num,0)) db_contingent_pct,
DECODE(pbn.pl_bnf_id, null, 'DeleteIconDisabled', 'DeleteIconEnabled') delete_switcher,
pen.pl_id pl_id,
pen.oipl_id oipl_id,
nvl((select 'Y' from dual where (to_date(:1 , 'rrrr/mm/dd') between
          nvl(pcr.date_start,to_date(:2 , 'rrrr/mm/dd')) and
          nvl(pcr.date_end,to_date(:3 , 'rrrr/mm/dd'))) and
          (pil.lf_evt_ocrd_dt <= nvl(con.date_of_death,pil.lf_evt_ocrd_dt))), 'N') rel_exists_flag
FROM per_people_f con,
per_contact_relationships pcr,
ben_pl_bnf_f pbn,
ben_prtt_enrt_rslt_f pen,
     ben_per_in_ler pil
WHERE pcr.personal_flag = 'Y'
AND (pbn.pl_bnf_id is not null or
(to_date(:4 ,'rrrr/mm/dd') between
nvl(pcr.date_start,to_date(:5 ,'rrrr/mm/dd'))
AND nvl(pcr.date_end,to_date(:6 ,'rrrr/mm/dd'))
          and pil.lf_evt_ocrd_dt <= nvl(con.date_of_death,pil.lf_evt_ocrd_dt)))     --Bug 4297137
AND pcr.contact_person_id = con.person_id
and pen.person_id = pcr.person_id
AND pbn.bnf_person_id (+) = con.person_id
AND to_date(:7 ,'rrrr/mm/dd') between pbn.effective_start_date (+)
AND pbn.effective_end_date (+)
AND pcr.person_id = :8
and pen.prtt_enrt_rslt_id = :9
and to_date(:10 , 'rrrr/mm/dd') between con.effective_start_date and con.effective_end_date
and to_date(:11 , 'rrrr/mm/dd') between pen.effective_start_date and pen.effective_end_date
and pil.per_in_ler_id = pen.per_in_ler_id
and pil.per_in_ler_stat_cd NOT IN('VOIDD', 'BCKDT')
and pbn.prtt_enrt_rslt_id (+) = :12
and ((to_date(:13 ,'rrrr/mm/dd') between
nvl(pcr.date_start,to_date(:14 ,'rrrr/mm/dd')) and
nvl(pcr.date_end,to_date(:15 ,'rrrr/mm/dd'))) or
((pcr.date_start = (select max(pcr2.date_start)
from per_contact_relationships pcr2
where pcr2.contact_person_id = pcr.contact_person_id
and pcr2.person_id = pcr.person_id
and pcr2.personal_flag = 'Y')) and
not exists (select null
from per_contact_relationships pcr3
where pcr3.contact_person_id = pcr.contact_person_id
and pcr3.person_id = pcr.person_id
and pcr3.personal_flag = 'Y'
and to_date(:16 ,'rrrr/mm/dd') between
nvl(pcr3.date_start,to_date(:17 ,'rrrr/mm/dd'))
and nvl(pcr3.date_end,to_date(:18 ,'rrrr/mm/dd')))
and (pbn.pl_bnf_id is null or
exists (select null from ben_per_in_ler pil2
where pil2.per_in_ler_id = pbn.per_in_ler_id
and pil2.per_in_ler_stat_cd not in ('VOIDD','BCKDT')))
GROUP BY pcr.person_id,
pen.prtt_enrt_rslt_id,
con.last_name,con.first_name,con.suffix,
con.full_name,
con.national_identifier,
pcr.contact_type,
con.date_of_birth,
con.person_id,
con.business_group_id,
pen.per_in_ler_id,
pl_bnf_id,
pbn.object_version_number,
pbn.effective_start_date,
pen.pl_id,
pen.oipl_id,
          pcr.date_start,
          pcr.date_end,
          pil.lf_evt_ocrd_dt,
          con.date_of_death
union
SELECT to_number(null) person_id,
pen.prtt_enrt_rslt_id prtt_enrt_rslt_id,
con.first_name ||' '||con.last_name || ' ' || con.suffix Beneficiary,
con.national_identifier Ssn,
sum(decode(pbn.prmry_cntngnt_cd,'PRIMY',pbn.pct_dsgd_num,0)) primary_pct,
sum(decode(pbn.prmry_cntngnt_cd,'CNTNGNT',pbn.pct_dsgd_num,0)) contingent_pct,
con.person_id bnf_person_id,
con.business_group_id,
pen.per_in_ler_id,
pbn.pl_bnf_id pl_bnf_id,
pbn.object_version_number object_version_number,
pbn.effective_start_date,
'SLF' contact_type,
con.full_name beneficiary_full_name,
sum(decode(pbn.prmry_cntngnt_cd,'PRIMY',pbn.pct_dsgd_num,0)) Db_Primary_pct,
sum(decode(pbn.prmry_cntngnt_cd,'CNTNGNT',pbn.pct_dsgd_num,0)) db_contingent_pct,
DECODE(pbn.pl_bnf_id, null, 'DeleteIconDisabled', 'DeleteIconEnabled') delete_switcher,
pen.pl_id pl_id,
pen.oipl_id oipl_id,
'Y' rel_exists_flag
FROM per_people_f con,
ben_pl_bnf_f pbn,
ben_prtt_enrt_rslt_f pen,
     ben_per_in_ler pil
WHERE
pbn.bnf_person_id (+) = con.person_id
AND to_date(:19 ,'rrrr/mm/dd') between pbn.effective_start_date (+)
AND pbn.effective_end_date (+)
AND con.person_id = :20
and con.person_id = pen.person_id
and pen.prtt_enrt_rslt_id = :21
and to_date(:22 , 'rrrr/mm/dd') between con.effective_start_date and con.effective_end_date
and to_date(:23 , 'rrrr/mm/dd') between pen.effective_start_date and pen.effective_end_date
and pil.per_in_ler_id = pen.per_in_ler_id
and pil.per_in_ler_stat_cd NOT IN('VOIDD', 'BCKDT')
and (pbn.pl_bnf_id is not null or pil.lf_evt_ocrd_dt <= nvl(con.date_of_death,pil.lf_evt_ocrd_dt))     --Bug 4297137
and pbn.prtt_enrt_rslt_id (+) = :24
and (pbn.pl_bnf_id is null or
exists (select null from ben_per_in_ler pil2
where pil2.per_in_ler_id = pbn.per_in_ler_id
and pil2.per_in_ler_stat_cd not in ('VOIDD','BCKDT')))
GROUP BY pen.prtt_enrt_rslt_id,
con.last_name,con.first_name,con.suffix,
con.full_name,
con.national_identifier,
con.date_of_birth,
con.person_id,
con.business_group_id,
pen.per_in_ler_id,
pl_bnf_id,
pbn.object_version_number,
pbn.effective_start_date,
pen.pl_id,
pen.oipl_id
ORDER BY 3,14
]]></SQLQuery>
<DesignTime>
<Attr Name="_isCodegen" Value="true" />
<Attr Name="_version" Value="9.0.3.13.75" />
<Attr Name="_CodeGenFlagNew" Value="36" />
<Attr Name="_rowSuperClassName" Value="oracle.apps.fnd.framework.server.OAPlsqlViewRowImpl" />
<Attr Name="_objectSuperClassName" Value="oracle.apps.fnd.framework.server.OAPlsqlViewObjectImpl" />
</DesignTime>
<ViewAttribute
Name="PersonId"
IsQueriable="false"
IsPersistent="false"
Precision="15"
Scale="0"
Type="oracle.jbo.domain.Number"
AliasName="PERSON_ID"
ColumnType="$none$"
Expression="'See the SQL...'"
SQLType="NUMERIC" >
</ViewAttribute>
<ViewAttribute
Name="PrttEnrtRsltId"
IsQueriable="false"
IsPersistent="false"
Precision="15"
Scale="0"
Type="oracle.jbo.domain.Number"
AliasName="PRTT_ENRT_RSLT_ID"
ColumnType="$none$"
Expression="'See the SQL...'"
SQLType="NUMERIC" >
</ViewAttribute>
<ViewAttribute
Name="Beneficiary"
IsQueriable="false"
IsPersistent="false"
Precision="332"
Type="java.lang.String"
AliasName="BENEFICIARY"
ColumnType="$none$"
Expression="'See the SQL...'"
SQLType="VARCHAR" >
</ViewAttribute>
<ViewAttribute
Name="Ssn"
IsQueriable="false"
IsPersistent="false"
Precision="30"
Type="java.lang.String"
AliasName="SSN"
ColumnType="$none$"
Expression="'See the SQL...'"
SQLType="VARCHAR" >
</ViewAttribute>
<ViewAttribute
Name="PrimaryPct"
IsQueriable="false"
IsPersistent="false"
Precision="15"
Type="oracle.jbo.domain.Number"
AliasName="PRIMARYPCT"
ColumnType="$none$"
Expression="'See the SQL...'"
SQLType="NUMERIC" >
</ViewAttribute>
<ViewAttribute
Name="ContingentPct"
IsQueriable="false"
IsPersistent="false"
Precision="15"
Scale="0"
Type="oracle.jbo.domain.Number"
AliasName="CONTINGENTPCT"
ColumnType="$none$"
Expression="'See the SQL...'"
SQLType="NUMERIC" >
</ViewAttribute>
<ViewAttribute
Name="BnfPersonId"
IsQueriable="false"
IsPersistent="false"
Precision="15"
Scale="0"
Type="oracle.jbo.domain.Number"
AliasName="BNFPERSONID"
ColumnType="$none$"
Expression="'See the SQL...'"
SQLType="NUMERIC" >
</ViewAttribute>
<ViewAttribute
Name="BusinessGroupId"
IsQueriable="false"
IsPersistent="false"
Precision="15"
Scale="0"
Type="oracle.jbo.domain.Number"
AliasName="BUSINESSGROUPID"
ColumnType="$none$"
Expression="'See the SQL...'"
SQLType="NUMERIC" >
</ViewAttribute>
<ViewAttribute
Name="PerInLerId"
IsQueriable="false"
IsPersistent="false"
Precision="15"
Scale="0"
Type="oracle.jbo.domain.Number"
AliasName="PERINLERID"
ColumnType="$none$"
Expression="'See the SQL...'"
SQLType="NUMERIC" >
</ViewAttribute>
<ViewAttribute
Name="PlBnfId"
IsQueriable="false"
IsPersistent="false"
Precision="15"
Scale="0"
Type="oracle.jbo.domain.Number"
AliasName="PL_BNF_ID"
ColumnType="$none$"
Expression="PL_BNF_ID"
SQLType="NUMERIC" >
</ViewAttribute>
<ViewAttribute
Name="ObjectVersionNumber"
IsQueriable="false"
IsPersistent="false"
Precision="9"
Scale="0"
Type="oracle.jbo.domain.Number"
AliasName="OBJECT_VERSION_NUMBER"
ColumnType="$none$"
Expression="OBJECT_VERSION_NUMBER"
SQLType="NUMERIC" >
</ViewAttribute>
<ViewAttribute
Name="EffectiveStartDate"
IsQueriable="false"
IsPersistent="false"
Type="oracle.jbo.domain.Date"
AliasName="EFFECTIVE_START_DATE"
ColumnType="$none$"
Expression="EFFECTIVE_START_DATE"
SQLType="DATE" >
</ViewAttribute>
<ViewAttribute
Name="ContactType"
IsQueriable="false"
IsPersistent="false"
IsNotNull="true"
Precision="30"
Type="java.lang.String"
AliasName="CONTACT_TYPE"
ColumnType="$none$"
Expression="CONTACT_TYPE"
SQLType="VARCHAR" >
<DesignTime>
<Attr Name="_DisplaySize" Value="30" />
</DesignTime>
</ViewAttribute>
<ViewAttribute
Name="BeneficiaryFullName"
IsQueriable="false"
IsPersistent="false"
Precision="240"
Type="java.lang.String"
AliasName="BENEFICIARY_FULL_NAME"
ColumnType="$none$"
Expression="BENEFICIARY_FULL_NAME"
SQLType="VARCHAR" >
<DesignTime>
<Attr Name="_DisplaySize" Value="240" />
</DesignTime>
</ViewAttribute>
<ViewAttribute
Name="DbPrimaryPct"
IsQueriable="false"
IsPersistent="false"
Type="oracle.jbo.domain.Number"
AliasName="DB_PRIMARY_PCT"
ColumnType="$none$"
Expression="DB_PRIMARY_PCT"
SQLType="NUMERIC" >
</ViewAttribute>
<ViewAttribute
Name="DbContingentPct"
IsQueriable="false"
IsPersistent="false"
Type="oracle.jbo.domain.Number"
AliasName="DB_CONTINGENT_PCT"
ColumnType="$none$"
Expression="DB_CONTINGENT_PCT"
SQLType="NUMERIC" >
</ViewAttribute>
<ViewAttribute
Name="Relation"
IsQueriable="false"
IsPersistent="false"
Type="java.lang.String"
AliasName="Relation"
ColumnType="$none$"
SQLType="VARCHAR" >
</ViewAttribute>
<ViewAttribute
Name="DeleteSwitcher"
IsPersistent="false"
Precision="30"
Type="java.lang.String"
AliasName="DeleteSwitcher"
ColumnType="VARCHAR2"
Expression="DeleteSwitcher"
SQLType="VARCHAR" >
</ViewAttribute>
<ViewAttribute
Name="PlId"
IsPersistent="false"
Precision="15"
Scale="0"
Type="oracle.jbo.domain.Number"
AliasName="PlId"
ColumnType="VARCHAR2"
Expression="PlId"
SQLType="NUMERIC" >
</ViewAttribute>
<ViewAttribute
Name="OiplId"
IsUpdateable="false"
IsPersistent="false"
Precision="15"
Scale="0"
Type="oracle.jbo.domain.Number"
AliasName="OiplId"
ColumnType="VARCHAR2"
Expression="OiplId"
SQLType="NUMERIC" >
</ViewAttribute>
<ViewAttribute
Name="RelExistsFlag"
IsQueriable="false"
IsPersistent="false"
Precision="30"
Type="java.lang.String"
AliasName="REL_EXISTS_FLAG"
ColumnType="VARCHAR2"
Expression="REL_EXISTS_FLAG"
SQLType="VARCHAR" >
</ViewAttribute>
</ViewObject>
Thanks,
Ronaldo

Set deletion indicator in purchase requisition account assignment

Hi Guys,
Can you please help we with the solution to set deletion indicator in purchase requisition account assignment or close purchase requisition. A purchase requisition of $3.600.000,00 was created through Project system Network-External Processing and it has 2 duplicate network activities and $2.246.577,20 was converted to purchase order then $1,353,423 became the network remaining order plan. A purchase order service entry sheet was accepted and the invoice was created. Now Iu2019m experiencing problem when Iu2019m trying to change WBS element and Network system status to TECO in order to remove the remaining order plan of $1,353,423. Iu2019m getting error message number:06411 the procedure I have follow to correct the error is to reduce quantities in the account assignment item and delete superfluous account assignment by setting deletion in each case but I cannot do that because the fields are grey
Regards
Sandile

Hi,
please check first if the report ZMO_CORRECT_EBKN from note 739004 can correct the problem.
I would like to recommend you to check also the note 796973 whether the correction is avalilable in your coding, it should solve the issue.
In case the problem still persists, please open a ticket to get help from the primary support in area MM-SRV.
Regards,
Edit

Purchase order creation - Account assignment group C (Sales Order)

Hello Gurus
During the purchase order creation in Me21N, account assignment category C (sales order) is available. In which scenario we will use it. When I assign C system is asking for a GL account. Why system needs a GL account, and how the posting will be at the time of goods receipt. Thanks for your help in advance.

Hi,
Creation of Purchase Order with t.code: ME21N with account assignment category C (sales order) is used for Time and Material Expenses with third party scenario and you need to enter sales order number and respective G/L account . In this scenario 1st a sales order is created with a material( material created DIEN material type) & then purchase order created with respect to sales order.
Here you provide service to your customer and this service you procure from your vendor, you just play middle role for providing and getting service.Standard DIEN material type designed for Sales usage only, so you create sales order for service material.Service master is used to get service from vendor with item category D with proper account assignment category as C
Example:
Material type DIEN is used for when you offer "SERVICE" to your customer.( The steps are (VA01,VF01,VF04,F-28), If u used HR module( you can used with sales order with t.codes are: CAT2,CATS_APPR_LITE,CAT7,PR05,PRRW,PRFI)
Service Master records(AC01)ESM is used when you procure "SERVICE" from your vendor.( Steps are: ME21N with Item Cat. "D" with Acc. ***. Cat. "C", ML81N,MIRO & F-53).
Regards,
Biju K

What is the purpose of GL account in the account assignment tab of PO scree

hi,
in the purchase order screen, in the account assignment tab, there is a field labelled as GL account. May i know what is the purpose of this gl account because as far as i am concerned we need to specify the vendor gl account (in the vendor master) and the stock account and GR/IR account in BSX and WRX transactions in OBYC respectively.
In that case what is the purpose of specifyin a GL account in the purchase order account assignment tab?

Hi,
The fact is quite simple - When you are buying the material, you can be able to define if this is for inventorization or for consumption. If it is for inventory replenishment, then the stock account will be debited during GR posting. Otherwise, P&L account will be debited. The G/L account you have seen in your PO is always needed in case of direct consumption. At the time of GR posting, the posting lines will be -
1)   For stock item:
Dr     Stock Account (BSX Transaction/Event Key);
Cr     GR/IR Clearing Account (WRX Transaction/Event Key)
2)   In case of non-stock item:
Dr     P&L Account (GBB/xxx Transaction/Event Key where xxx is defined in the 'Account Modifier field of the related account assignment category setting in OME9 transaction - which is seen in the PO);
Cr    GR/IR Clearing Account (WRX Transaction/Event Key).
Cheers,
HT

Reg:Account Assignment

Hi
I have created PO doc type as ZCAP (for Capital items).whenever we select this doc type we have to select account assignment "A" in Acc.*** Category field in PO line item.As it is manual entry, user (by mistake) is giving "K" instead of "A".
My question how can i make "A" as default to doc type ZCAP.so that whenever we select ZCAP, automatically acc.assign "A" should come and all other account assignment categories should be deleted.
plz suggest me some way.
Thanks in advance.
Regards,
JNRKMM

Hello
There is no standard configuration to control the account assignment with Purchase order document type. Purchase order document type is an header level control where as the account assignment is Item level comtrol.
You need to use Badi to control the account assignemnt category at PO line item level with reference to the PO document type.
Please consider the Badi ME_PROCESS_PO_CUST
Application components: MM-PUR-PO, MM-PUR-PO-GUI : Main program: SAPLMEPO
The Business Add-In (BAdI) ME_PROCESS_PO_CUST enables you to extend the business logic of the Enjoy purchase order on an individual basis. You can thus influence the dialog transactions ME21N, ME22N, ME23N, and ME29N, and the BAPIs BAPI_PO_CREATE1 and BAPI_PO_CHANGE.
Typical applications for this BAdI include:
Processing of own objects
Processing of additional data on standard objects
Implementation of additional checks and derivations
Change of data in standard fields
1. Start of transaction
Documentation for BADI method INITIALIZE
2. Opening of a PO
Documentation for BAdI method OPEN
3. Checking of data
Header data of PO
Documentation for BAdI method PROCESS_HEADER
Item data of PO
Documentation for BAdI method PROCESS_ITEM
Delivery schedule lines of PO
Documentation for BAdI method PROCESS_SCHEDULE
Account assignments in PO
Documentation for BAdI method PROCESS_ACCOUNT
Processing of Account Assignment Data
Functionality
The PROCESS_ACCOUNT method enables you to change the account assignment data and check it for correctness.
Parameters
The following parameters are available:
IM_ACCOUNT - Account assignment
The interface reference is of the type IF_PURCHASE_ORDER_ACCOUNT_MM. You can use all methods defined there.
Note
Please note the general hints on Error Handling.
If you wish to mark the account assignment data as invalid, use the method INVALIDATE() of the IF_PURCHASE_ORDER_ACCOUNT_MM interface.
Pleae contact Technical consultant to implement the same
warm regards
Ramakrishna

PO account assignment : blank vs P vs Q

Hi,
I'm a newbie in MM. recently, there's a need to make PO material stock which is the inventory posting should be directly to inventory account, but it also needs to trace the cost into WBS.
i've already tested some ways below:
1. create PO material stock with blank account assignmet.
==> the mapped GL account is correct (inventory account) but impossible to input the WBS
2. create PO material stock with account assignment is set to P.
==> WBS can be inputted, but the mapped GL account is wrong (mapped to Expense)
3. create PO material stock with account assignment is set to Q.
==> both of GL account and WBS are possible to be inputted, but when i want to post, error message "Enter WBS element" always pop up, although i've already input the WBS.
anyone could help me?
Thanks a lot
Nasikhin

Hi
In the PO material stock with account assignment Q you need to specify the WBS elemnt in the account assignment tab of the PO Line item.
At the time of MIGO for GR using 101 the Stock will be posted into the Inventory account & with Special Stock indicator P - Specifying as project Stock.
The same can be checked out using MMBE
Once the material is consumed using 221 Q in MB1A then the consumption accounts get trigerred.
Thanks & Regards
Kishore

Error while creating a PO with Account assignment

HI MM Gurus
In our case, we need to create the STO for account assignment cat `Unknown`.
In SPRO I maintained combination of account assign cat and item cat.
Now, while creating a PO with Account assign U we get Error message - ME069 :Unknown account assignment not defined for use here.
Please advise how to resolve this issue.

Hi
When you are posting actuals, you need to give true account assignment object. With U (unknown), system cannot identify which account to be posted. Change account assignment in PO to another.
In standard SAP Unknown account assignment is not allowed in PO's. Only exception is Blanket PO.
Unknown is allowed only in PR and Blanket PO.
The reason is logically you are releasing the PO to the external vendor or Plant in this case you must know the account assignment.
Regards,
Ninad Kshirsagar

Purchase order : get Account assignment into BADI

Hi,
i'm using the BADI ME_PROCESS_REQ_CUST method POST ; in this method i need to access to items and it's work (i use im_header->get_items( ) ). But now i need to access to Account assignment, how can i do this ? the only object available is im_header.
Be careful, i can't read database because when i create a new document, the data are not saved again.
Thanks for help.
Cheer

IM_HEADER->get_items( ) returns the internal table RE_ITEMS type ref to MMPUR_REQUISITION_IITEMS (of line type MMPUR_REQUISITION_ITEM) which gives the list of line items.
Loop through the internal table RE_ITEMS, refer to the component RE_ITEMS-ITEM (type ref to IF_PURCHASE_REQUISITION_ITEM) & use the method RE_ITEMS-ITEM->IF_ACCT_CONTAINER_MM~GET_ITEMS( ) to get the account assignment details related to each item. This method is to be called in the loop for each line item.
Regards, Vinod
P.S : Is it purchase order or Purchase requisition ? By going through the post it is PR, your subject line seems to be wrong.
Edited by: Vinod Kumar on Jul 15, 2011 2:21 PM

WBS in Account assignment of Sales Contract

Dear Experts,
I am going through an old sales cotnract in VA43, and i came accross the account assignment tab where there is WBS field.
When does a sales guy use that. I thought it was only used for projects and ultimately an asset.Please advice coz this is new to me
Burzes

So do u mean that when you are performing or completing tasks for the customer you use a WBS?
Please reply
Thanks
Burzes

ME21N, Account Assignment, to set G/L Accout field 'read only

Similar Messages

Maybe you are looking for