No sufficient record found in control table for XXXX//X XX.XX.XXXX

When im trying to post an invoice for a customer, i found this error "No sufficient record found in control table for company code xxxx//x".

Asked some friends and after some checkings here is the problems : the number range for tax (faktur pajak) is not maintained yet for current year.

To solve it, access :

Cross Application Component --> General Application Functions --> Cross Application Document Numbering --> *choose country* --> Document Numbering --> Assign Number Ranges to Business Places/Company Code.

This step has to be done yearly or you can set it up for few years ahead at the beginning of the implementation.

Message no. FF 802 An exchange rate type is not defined for country ID

Yay! Got a new error, after lurking for a while...here is the solution : Cek the country setting (OY01) and set the exchange rate type. Dunno why this is happening tho T.T

Setting Number Range for CO Documents

Whoops!!! First time trying to set number range for CO Document! I went straight to IMG and access the maintain number range under Controlling menu. And...Its BLANK!

Mmm...supposedly there are business types to be assigned to groups and the groups are to be assigned to number range. What happened?

I found out that those business types are not going to appear automatically. You have to generate program RKTKA04C which functions to refresh the business types list.

So what i do was :

1. Run report RKTKA04C from SE38

2. Create Group for Business Types and assign number range to each group

3. Assign business types to the group

And~ VOILA! all done and CO documents can be created

Transport Request

Transport request basically is a code that's use to identify objects from one SAP client to another SAP client or environment to environment by using transport objects.

The code will automatically appears whenever we make a change to a configuration table or program.

Tcodes related are :

SE10 : maintain transport request

STMS : transport management system

SCC1 : to copy transport request from 1 client to another client in the same server

Setting Cost Element to be created automatically when creating GL Account

Okie~ the problem now is how to set the cost element to be created automatically when we create a GL account.

I'm pretty sure we can set this in the customizing but i'm totally forgot, sooo..after a while checking here and there and of course asking people, this is how you set it :

1. Step 1 : Customize the Chart of Accounts

SPRO --> FI New --> General Ledger Accounting New --> Master Data --> GL Account --> Preparations --> Edit Chart of Account Lists .

Here, double click at your Chart of Account (COA). In the tab "Integration" , set the Controlling Integration to "Automatic Creation of Cost Elements". However, if you set this, then every time we create a Profit/Loss GL Account, the system will automatically create the Cost Elements. If the user desire t0 not controlling internally every P/L GL Account, then avoid this customizing. Instead choose "Manual Creation of Cost Elements"

2. Step 2 : Check the Automatic Generations of Cost Elements

SPRO --> Controlling --> Cost Element Accounting --> Master Data --> Cost Elements --> Automatic Creation of Primary & Secondary Cost Element --> Make Default Setting

Set all the number range of cost element for the COA maintained at step 1. Here you should maintain which cost element number range goes to which Cost Element Category.

For Example : Account 40000000 to 499999999 goes to Cost Element Category 11 (Revenues).

GA733 : Segment Contains No Receiver

Been a week trying to solve this problem, and today i found out that this message appears on Profit Center Allocation if we try to allocate based on Statistical Key Figures. And this is also original bug from SAP. To solve it, check on SAP Note 114014. For version 4.0 and 4.5a please check directly to service.sap.com/notes.

What i do was :

1. Running GS09 (Copy sets from source client) and enter the delivery client at 'Source client' and the name of the account group 'INT_SPACE' at 'Set ID'.
2. In KDH1, i created a new account group 'XXXX_SPACE' for the chart of accounts 'XXXX' (it is derived automatically from the current controlling area!). Use the account group 'INT_SPACE' as a reference for the chart of accounts 'INT'. Save the new group without changing the entries.
3. When creating an assessment / distribution cycle, enter the account group 'XXXX_SPACE' ('XXXX' refers to the chart of account of the current controlling area) in field 'Account number' as a selection criterion of the tracing factor.

Error Missing Export Data

This error popped up when client updating a customer's country after creating sales order.

Apparently the error appears due to differences between Sales Organization Country & Ship to Party Country. This is how to fixed it. Taken from a good answer at SAP Community Network posted by Reazuddin MD http://forums.sdn.sap.com/thread.jspa?threadID=1551384.

Check- Incompletion procedure what are the fields maintained for Header / Item

IMG - SD- Foreign trade/Customs - Incompleness Schemas for Foreign trade data (VI29) & Foreign trade data in MM&SD (VI49)

if you dont want to maintain any fields in billing, Create new incompletion procedure for Header & Item, dont maintain any fields.
Assign this incompletion procedure in VI49.

Also posted by Calauz Artur :

In VF02 check the log for export data at heather level and item level, and fill those fields, the accounting document will be created.

the nature of LSMW

LSMW - Legacy System Migration Workbench

This is the common tool used in SAP R3's data migration. Supposedly 2 tools available : LSMW and BAPI. However, BAPI is a function, therefore we need to develop an ABAP program which includes the selected BAPI function before we can use it.

LSMW on the other hand is a ready to use migration tool. There are 4 import methods available in LSMW :

- Standard Batch/Direct Input - using the standard batch

- Batch Input Recording

- Business Object Method (BAPI)

- IDoc (Intermediate Document)

As for me, i'd prefer using Batch Input Recording which means i recorded the transaction manually and so the field which i fill is only the mandatory field and those i chose during the recording session.

LSMW also server dependent. Once you created an LSMW object in one server, it can be use in any clients available in the server. To copy one LSMW object or project from one server to another, we use the Export-Import option. First export the selected object (including the recorded object) to your local computer then Import the file at the other server.