on 08-24-2006 10:33 AM
In the ECC5.0 release,I can't change the Account Assignment Category in a service position, if I derive the Purchase Order from a Purchase Requisition.
I.E.: I create a PR for service whit K Account Category for all sublines, the PO I created by this PR, don't allow me to change Account Assignment Category.
The problem there isn't for materials.
There is a solution for this matter?
Ciao Fabio,
Please, kindly check the information contained under the SAP note:
366850 ME21N ME51N Service accnt assignmnt ready for input
360632 - ME21N Various improvements for account assignments.
As stated in it:
"Ad point 6)
It is now possible to change the account assignment category from
'Unknown' to something else. Not however from (for example) 'cost
center' to something else. This restriction only applies to service and
limit items. The field selection must also be set as a prerequisite as
described in Note 313120".
What these notes have done is to make this process an EXPLICIT one; by
making the Account Assignment TAB not changeable when services or limits
are involved. Before, the Acct Assgmt TAB was open for entry, which
confused users in thinking that they could maintain the data there,
wherin reality, they couldn't (and they thought it was a bug and logged
many problems with us).
Hope this information helps you.
Regards
David
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi David,
I solved the problem following the OSS note:
313120 - ME21N:Accnt assgmt cat fr item cat D cannt be chngd
Now I can change AAC normally from 'U' to something else.
In my test after customization I realize that I can change AAC from 'K' to something else in services POs too, only when I start creating my PO (derived from PR).
The field AAC become unchageable when I fill in a field in the Purchase Order (for example purchasing organization) before modify Account Assignment Category...I think it is a very strange behaviour for standard environment, do you have any suggestion?
Hi Fabio,
As far as I know that´s the standard behaviour. There are some checks in the system at the time of creating a PO, so when you fill any field the EKPO-KNTTP remains unchangeable.
You can check that this is hard-coded this way in program
SAPLMECO, in include LMECOU04 :
IF I_PSTYP EQ PSTYP-DIEN OR
I_PSTYP EQ PSTYP-BLNK.
Dienstleistungspositionen nicht ändern
MESSAGE E456(ME) WITH I_KNTTP RAISING CHANGE_NOT_ALLOWED.
ENDIF.
Review note 570767 as well.
This is hard coded so you can not change the account assignment. Please
see the below code. You can set a breakpoint and test this.
SE80
FUNCTION Group MEPO
Classes (Implementation)
LCLFS_MMMFD_ACCTASSCAT
*
CLASS LCLFS_MMMFD_ACCTASSCAT IMPLEMENTATION
*
........ *
*
CLASS lclfs_mmmfd_acctasscat IMPLEMENTATION.
METHOD lif_field_sel~execute.
DATA: l_t134m TYPE t134. "n_932533
IF NOT ls_local-ekpo-ebelp IS INITIAL.
IF ( NOT ls_local-ekpo-packno IS INITIAL AND "360632
NOT ls_local-ekpo-kzvbr EQ kzvbr-unbe ) OR "570767
ls_local-ekbes-wemng NE 0 OR "603064
ls_local-ekbes-wesbs NE 0 OR "717799
ls_local-ekbes-glmng NE 0 OR "785587
( ls_local-ekko-bsakz EQ 'T' AND "785587
ls_local-ekbes-wamng NE 0 ) OR
ls_local-ekbes-remng NE 0 OR
ls_local-ekbes-anzal NE 0 OR
ls_local-ekbnk-ebelp NE 0. -> Breakpoint
switch_field_to ''. ->('' means display)
ENDIF.
Regards
David
User | Count |
---|---|
107 | |
12 | |
11 | |
6 | |
5 | |
4 | |
3 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.