Goods Receipt/Issue Slips Configuration

In Inventory Management there are out put document such as goods receipt slip, issue slip, & etc that can be printed for every movement. You can print the form via t-code MB90 with output type as option to print. Output type is code to define what form you want to print.

Example:

Your client want to print goods issue slip with two different format. With this condition you have to create two output type code and attach the form into this output type.

Solution:

You have to configure difference output type for difference format slip, and create difference sap form for difference slip/form.

Error while AUC settlement

While my client settle AUC into new fiscal year which acquisition on old fiscal year, error “Settlement of Old Asset Data to Receiver Type G/L Not Allowed” happen. Full message from SAP you can see like below:

Message from SAP :

Settlement of Old Asset Data to Receiver Type G/L Not Allowed
Message no. AW607Diagnosis
You tried to settle values from the previous year to a receiver other than
an asset. This procedure is not supported by the system.

Procedure
Check your distribution rules and change the receiver.

I have been check the distribution rule of AUC, 80 % settle into fix asset and 20% settle into G/L expense. This problem happen only if the AUC settlement is running on different fiscal year (acquisition on old fiscal year, and settlement on new fiscal year). Based on the message I conscious that SAP configuration does not allow for this distribution in different fiscal year.

I’ve been think for an hours for this problem and finally I got idea for the solution. First, I change the distribution rule from fix asset and expense into AUC. And then run the settlement, after that the distribution rule change into fix asset and expense and run again the settlement…. Thanks God its working.

Changing the SAP Standard – Transaction Variant

In some business, sometime we need to adjust business transaction by hiding all information not relevant and displaying only the important information.As a case, asset master data maintenance only permitted to change only General data. In this case you have modify the screen of asset maintenance, for detail case see image below :

Standard : display screen of AS02.

Learning BAPI from Asheet Bephora

Well, right now I produce many of BAPI for my client to handle interface between SAP with other system. In this Blog I just want to say thanks for Asheet as my instructor while learning BAPI on EISPL Singapore. I still remember while learning, always asking and asking because I’m new in ABAP experience. It’s about 2 years ago, so long…. and I hope we will meet again. Below my picture with Asheet :

And below is my testimonial on EISPL : http://www.eispl.com/testimonials/SAP_training_16.html

Well, it’s only memorial article. Thanks for Asheet, thanks for Mas Adi – you give me night in Singapore.

Finding Email address Customer and Vendor Master on SAP

It’s not quite simple to find email address of Customer and Vendor Master on SAP. You need to activated SQL trace and change email on master to find where email address is stored. Here i share the result of tracing using SQL trace of email addess Customer and Vendor master.

For Customer :

select adr6-addrnumber (email) from table adr6 join table kna1 with key adr6-addrnumber = kna1-adrnr

For Vendor :

select adr6-addrnumber (email) from table adr6 join table lfa1 with key adr6-addrnumber = lfa1-adrnr

ABAP Version :

data : lv_email like adr6-addrnumber.

select addrnumber into lv_email from adr6 as a  inner join kna1 as b on a~addrnumber = b~adrnr.

Get comments texts from SAP

In many transaction, SAP stores comments in different table. For example if you want to get comments texts on Item detail of Purchasing order , belive me you will not find on table EKPO (Item table of purchasing order). So you need a function and some object or id to get the comment. You can find object by entering table STXH-TDNAME with Purchasing order number plus asterisk (because STXH-TDNAME contains PO Number plus Item number of PO). STXH-TDNAME = ’4500002131*’ will be bring back object, name, and id as parameter on function module READ_TEXT.

The following code is a function that will return PO Item text :

Improving WIP Calculation

My client has been decided to change the production strategy from discrete manufacturing to repetitive manufacturing. Discrete manufacturing produce production order,  and the problem is many production order pending (status is not closed).

As a result of the above condition, WIP calculation  performance is getting down from one hours become a day and finally WIP calculation is not run properly.

I found some note from SAP library, give me some tips how to improve WIP calculation performance. The note said that you can significantly improve the performance of WIP calculation by setting the status DLFL (Deletion flag)  for the following orders:

·         The order is delivered or technically completed

·         Variances have been calculated for the order

·         You do not anticipate any further follow-up costs for the order

Practically I do the following action above and finally the performance of WIP – calculation was improved significantly.

 

Appendix :

WIP : Work in process

Release code on relation with table EBAN (Purchase Requisition)

Well, finally I found how to get release code on relation with table EBAN (purchase requisition), after 3 ours searching. I need this because my client need to build a query with out put purchase requisition release information. Basically I found the table by debugging function module “BAPI_REQUISITION_GETRELINFO”, this function module gather all information about purchase requisition release strategy. Below is detail relation between the table : 

EBAN-FRGGR = T16FS-FRGGR -> Release Group

EBAN-FRGST  = T16FS-FRGSX  -> Release strategy

SQL error “-904″ occurred when accessing table “COSS”

              While my ABAP source code trying to select the contain data of table “COSS” using Contain Pattern in once of condition, short dump with error “SQL error “-904″ occurred when accessing table “COSS “” happen in my development client with no specific error analysis given from SAP short dump system. I thought that some SQL package is not properly working, thus I decide to delete the SQL package  and restart the machine, but error still happen.           

              I try to debug my program, and I found that ABAP SQL cannot accept more than 200 records data of contain pattern as selection criteria, my head is still in question…why…? what happen…?. And finally I split the data (Contain Pattern) in a hundred records, it’s mean that when accessing table “COSS” is only limited a hundred records of contain pattern as selection parameter, and it’s working.See the ABAP source code below :

Change the development class for a customer screen

Here some tips to change development class for a customer screen :

1. Call Transaction SE03: “Workbench Organizer: Tools.”
2. Expand node: “Object directory.”
3. Choose “Change object directory entries of objects.”
4. Enter key fields R3TR FUGX and select line.
5. Enter (for example): XM02 as contents of the key field.
6. Start the selection.
7. Position your cursor on the selected entry: FUGX XM02.
8. Choose function: “Change object catalog entry.”
9. Change and save the development class.