Set Company Code to Productive

HI,

The field 'Productive' can be set in either transaction OBR3 or OBY6.

The field 'Productive' is a flag for some deletion programs

For example the following programs check this flag and return

an error if this flag is set:

SAPF019 -> Deleting master data

SAPF020 -> Reset transaction data

SAPF023 -> Reset bank data

This prevents deletion programs from resetting data in a company code

by mistake. This is the only implication as far as we are aware and SAP

recommend the flag to be set. If necessary (eg for deletion purposes),

this can be reversed.

The recommendation from SAP is that you to set it in all systems.

The recommendation would be if you wish to have the flag set then to

set in your development system therefore the flag indicator is picked

up with every transport from the development system. There would be

no reason to remove this indicator in your development system.

Reg

Madhu M

Hi,

Setting this indicator ensures data integrity and avoids accidental data loss.

If this indicator is not set to productive it is possible to reset (delete) an entire company code or all posted depreciation amounts with a single click. Since SAP does not require you to set your company code to productive, many companies do not set it properly, leaving it on test mode, which was required during implementation to ensure that test data loaded correctly. Many companies simply go live with the test setting still in place and never bother to check this flag until errors occur.

A company code not in productive mode allows a user to run asset data takeover transactions such as AS91 (create old asset) or AS92 (change old asset). These takeover transactions allow you to load (or take over) your old asset master records and values into the sub-ledger. For this to happen, you must set the company code status to test mode (2) or data-load mode (1). These transactions update the FI-AA sub-ledger, but do not update the G/L. In other words, you can use these transactions to sync up the sub-ledger with the G/L. This is a great feature during initial data loads, but obviously not something you would want to run after you go live.

In addition to these takeover transactions, a company code not set to productive status allows a user to run reset transactions. These transactions can reset posted depreciation amounts in FI-AA (transaction OAGL) after which you would have a serious imbalance between the sub-ledger and the G/L. You even could reset an entire asset company code (transaction OABL), which means deletion of all master records and transactions. Again, these are very useful transactions when you first go live, but after that you want to ensure that there is no way someone could execute these transactions accidentally.

To set the company code status to productive, which does not affect other modules, go to the IMG for FI-AA and follow the menu path Preparing for Production Startup>Production Startup>Activate Company Code .

The indicator should be set to 0 or left blank, which both indicate productive status, once a company code is live . Set this status simply by typing in the number and saving the transaction.

you always can set the indicator back to 2 (test status u2014 everything is allowed) or 1 (data-load status u2014 only takeover transactions are allowed).

However, setting the status as 1 or 2 when you go live unnecessarily exposes your company to real risks, such as resetting posted depreciation or an entire company code.

Regards,

Praisty

Hi,

You can perform now.

This prevents deletion programs from resetting data in this company code by mistake.

Thanks

Hi Roy,

This option is available at company code global data (OBY6)

If you select that company code which is working productively should be indicated here by an "X". This prevents deletion programs from resetting data in this company code by mistake.

Regards

Surya