01-05-2011 8:13 PM
We are using the new GL in ECC 6. I have a strange problem where special fields that were added to the line item transactions display in dev and quality but not in production. Please read the steps that I have taken.
1. Using note 984305 we defined special field BSEG-MATNR using this path:
Financial Accounting (New)
General Ledger Accounting (New)
Master Data
G/L Accounts
Line Items
Define Special Fields for Line Item Display
This field (U_MATNR) displays correctly in FAGLL03.
2. I used note 1034354 to create an implementation of BAdI 'FAGL_ITEMS_CH_DATA. Then I
followed the documentation of the BAdI to create structure CI_FAGLPOSX within FAGLPOSX and added these fields:
Material Type: field MARA-MTART
Material Group: MARA-MATKL
I added code to method CHANGE_ITEMS to read for those fields. Here's part of the code:
* MARA - Get Material Type and Material Group
SELECT SINGLE mtart matkl
FROM mara
INTO (wa_items-zzmtart, wa_items-zzmatkl)
WHERE matnr = wa_items-u_matnr.
The values of these fields display correctly in development and quality, but they do not display in production.
3. When I debugged FAGLL03 in development I found that the value of U_MATNR was filled when I stopped at method CHANGE_ITEMS. However, when I debugged in production, U_MATNR was not filled. It had to be filled at a later time because the value appears on the report. In my code, I am using U_MATNR to find the values of material type and material group. Because U_MATNR doesn't have a value at that point in time in production, my code doesn't find material type or material group.
4. I contacted SAP and was instructed to use note 984305. I executed the function module
ITEM_STRUC_EXTENSION which did not help.
5 I also used note 205096 to execute report BALVBUFDEL, but this did not help either.
6. At this point, SAP told me that it is a consulting issue. I'm not sure that it is because I'm using SAP solutions without modifying anything.
7. I tried to compare configuration between development and production, but everything looked OK to me.
Has anyone had this problem? Any tips?
Brenda
01-05-2011 10:51 PM
Hi Brenda,
>
> 6. At this point, SAP told me that it is a consulting issue. I'm not sure that it is because I'm using SAP solutions without modifying anything.
I have no idea except that you can make sure Include CI_FAGLPOSX is active as well as the including FAGLPOSX. And please check the transport protocol(s) if CI_FAGLPOSX is included. If you have any kind of error/warning in the import protocol, that may give you a hint.
If nothing helps, create a new sap support case and tell them you are using SAP solutions without modifying anything.
Regards,
Clemens
01-06-2011 1:19 PM
Clemens,
Thank you for your suggestions. I checked the includes and they are all active. My transport also included CI_FAGLPOSX and there were no errors within the transport process.
I liked your .
Brenda
02-11-2011 1:32 PM
I opened a new SAP support case as Clemens recommended. Once again I was told that my problem was a consulting issue, so I got our customer service rep involved. At that point the consultant checked our system. He ran the report BALVBUFDEL which seemed to solve the problem. I'm not sure how that worked since we had previously run the same report, but the problem is fixed.
Brenda
01-05-2011 10:55 PM
Hi Brenda,
It would be nice if it worked the way the notes indicate it should - however would it be simpler to look up the value of MATNR in the CHANGE_ITMS method at the same time as looking up the material type and group?
It's an extra select as you can't do a join to BSEG so you'd need to be careful of performance as well.
Alternatively can you debug to determine where U_MATNR is getting filled?
Cheers
Alex
01-06-2011 1:16 PM
Run Function "LINE_ITEMS_SPECIAL_FIELDS" with parameter I_TYPE_LIDIS = '1'.
In you production-system.
01-06-2011 2:02 PM
Hello steiner fisher,
Could you please tell me a little more about this function module and why I should execute it in production?
Brenda