Mostrando las entradas con la etiqueta English. Mostrar todas las entradas
// //

System Messages in ECC 6.x

We are now using SAP ECC6.0 version. The SAP system only displayed system messages that were created after the first login of user. After re-logon again by using the same SAP ID, the system messages are displayed anymore.
The system messages should be displayed everytime loging on SAP system as SAP 4.6c version.

Due to as of SAP release 6.x, the system messages are only displayed once a day. If system messages need to be restored the old behavior as SAP old version, and SAP system should displayed SAP messages again after each login activity.

How to always display system messages after each login activity:

Must activate the first SELECT statement and the error handling in function module SM02_GET_UNREAD_MESSAGE in function group SM02.
Implement correct instruction in SAP Note 604495

Via Sap-exp.com
Leer más ...
// //

SAP FI CO OVERVIEW

FINANCIAL ACCOUNTING OVERVIEW

The Financial Accounting (FI) module is the core module within the financials application. Almost all functionality that resides in the other financial application modules relies on the implementation of at least parts of the FI module. Financial Accounting is designed to provide financial information from an external view. The main FI components offer functionality for the general ledger, accounts receivables and accounts payables, asset management, a special ledger used to meet user specific requirements, funds management, and legal consolidations. The general ledger (G/L) houses the chart of accounts as well as the account balances and line items. The G/L tracks all transactional postings, such as inventory updates, sales revenues, bank accounts, and expenses. Accounts Receivable (AR) and Accounts Payable (AP) are subledgers of the G/L that support the processes involved with the collection of revenues and payments of expenses. Combined AR and AP facilitate maintaining customer or vendor records, account balances and line items, payments, clearing, advice notices, dunning, interest calculations, check releases, and over/underpayment management. The AR/AP information systems support reporting for due date breakdown, payment history, days sales outstanding, overdue items, and currency risk. Asset management is another subledger to the G/L that focuses on the management of the fixed assets in an organization. Asset management maintains the master records for the assets, special valuations, country-specific requirements, and four types of depreciation calculations, one of which is for cost depreciation. The special ledger functionality supports the ability to create other ledgers or subledgers for specific user requirements. Special ledgers can pull information from other modules and can support simplistic allocations. In addition to the ledgers and subledgers, FI contains functionality supporting funds management and legal consolidations. Funds management provides the capabilities to define planned revenues and expenses for the management areas, monitor these transactions as compared to available funds, and prevent exceeding the budget. Once all transactions have been completed, consolidations can be performed. Legal consolidations functionality supports providing consolidated financial information for companies and business areas. Business areas are utilized primarily for external reporting of business segments across companies.

Leer más ...
// //

Client Copy

Client copy showing the status as "Post Processing Required".

Nearly 250 tables were not copied.
Giving Warning in FIN-BN component.

In SM37 the client copy job is Successfully Completed.

I am not sure whether the client copy is completed successfully or not..

Leer más ...
// // 1 comentario

Client Copy: Derivation rule tables

Client copy is completed with status "Post-Processing Required". There is an error in log for object FINB-TR-DERIVATION:
DA300 "No active nametab exists for *some db table*"

Name of db table is usually with naming convention:
xxyyyysssmmmnnnn (xx - application class, yyyy - strategy ID, sss - system indicator, mmm - client, nnnn - sequence number)

These db tables are part of some instance of derivation tool in your system and are used to store Derivation Rule Values.
Other terms

ABADR, FINB_TR_CC_EXIT, FINB_TR_CC_EXIT_TARGET, DA 300, DA300, CC, SCC9, SCCL, SCC3

Reason and Prerequisites

During processing CC there was huge workload into your system. CC processcreates new tables to store copied derivation rules. This is done in parallel asynchronous process. But due to workload into system, these tables weren't created as fast as needed by CC process.
CC process cannot access these tables to save derivation rules in target client, as mentioned also in log.
Solution


HOW TO FIX CURRENT CLIENT COPY
(All steps to be performed in target logical system)

      1. Decrease workload as much as possible

      2. Execute report ABADRCHECK with selected 'DELSTEPS'
      (see note 653314 for more details)

      3. Execute TCode FINB_TR_EXEC_AI (Postprocessing of Client Copy)   (Please note that any changes done between Client Copy and          executing TCode FINB_TR_EXEC_AI will be overwritten!)

      4. Result of FINB_TR_EXEC_AI execution

            a) Executed with same error DA 300
            The workload is still to high, make sure that workload is decreased and repeat steps 1. - 3.

            b) Executed without any errors
            Consider FINB-TR-DERIVATION part of Client Copy as completed successfully. Note, that status of Client Copy in TCode SCC3 "Post-Processing Required" is final and it's not updated based on successful execution of FINB_TR_EXEC_AI.

            Information about final Client Copy status need to be evaluated and kept outside of SAP system. Or optionally, the client can be protected against any further manually triggered post processing procedure (e.g. using TCodes FINB_TR_EXEC_AI, FINB_TR_DISPLAY etc.) using the IMG activity "Complete Postprocessing". It's suggested to do so, when Client Copy is successfully repaired by repetitive execution of post processing procedure.


WHAT TO DO BEFORE NEXT CLIENT COPY
Make sure that there will be no performance issues during Client Copy processing in target logical system.
Leer más ...
// //

FAQ: Data Browser (SE16)

[1] Why does the results list of the SE16 transaction display the content of some fields differently from the detailed view?
[2] Why can I not change a table in the SE16 transaction although the table was selected as changeable in the SE11 transaction under Attributes?
[3] Why can the smallest value in the results list differ with a different value for the 'Maximum number of hits'?
[4] Which authorizations does a user require to display certain values in the SE16 transaction?
[5] How can I search for special characters?
[6] Why are texts from text tables not displayed?
[7] Why can I only create user-specific variants in the ALV list?

[1] Why does the results list of the SE16 transaction display the content of some fields differently from the detailed view?

 Examples:
Table Field Hit list display Detail view display
BSIS HKONT 0000191100 191100
MARA MEINS ST PC
T002 SPRAS b IS

Answer:Conversion exits are defined for some domains of the table fields.These are processed with each screen input or output.The default hit list is not a screen, therefore, the conversion exit is not processed.You can, however, include the exit in the processing using the 'Settings'->'List parameters' menu option.

[2] Why can I not change a table in the SE16 transaction although the table was selected as changeable in the SE11 transaction under Attributes?
Answer:
The changeability of table entries still depends on the following factors:
    - Role and changeability of the client;
    - System changeability;
    - Delivery class of the table;
    - If a maintenance view for the table exists:
    - Authorizations.
Refer to note 109083 for more information.
Leer más ...
// //

FAQ: Upgrade PREPARE

1. When should I start the PREPARE?

Start the PREPARE as early as possible before the upgrade so that you can set up or carry out the necessary preparations in good time.

2. Can I repeat the PREPARE?

You can repeat most of the PREPARE modules as often as you like without resetting the entire PREPARE. You must reset PREPARE only when you make bigger changes to the source release, for example, if you import software such as SAP Support Packages, languages or add-ons (including add-on updates) after the PREPARE is started. In general, however, you should ensure that the relevant modules are completely executed before resetting the PREPARE as described in the upgrade guide. Keep in mind that resetting only changes the status for the upgrade and does not undo any PREPARE database operations.

3. Must I include Support Packages in the upgrade?

We generally recommended that you include Support Packages; otherwise, depending on the Support Package level of the source release, the system carries out a downgrading of objects. This may cause data losses and/or problems in some upgrade phases. For more information, see Notes 73510 and 119738. Furthermore, this is often the quickest method of importing Support Packages.

Leer más ...
// //

What are Functional Specifications?

Functional specifications (functional specs), in the end, are the blueprint for how you want a particular report and transaction to look and work. It details what the report will do, how a user will interact with it, and what it will look like. By creating a blueprint of the report or transaction first, time and productivity are saved during the development stage because the programmers can program instead of also working out the logic of the user-experience. It will also enable you to manage the expectations of your clients or management, as they will know exactly what to expect.

A key benefit of writing up a Functional Spec is in streamlining the development process. The developer working from the spec has, ideally, all of their questions answered about the report or transaction and can start building it. And since this is a spec that was approved by the client, they are building nothing less than what the client is expecting. There should be nothing left to guess or interpret when the spec is completed.

Functional Specification
A functional specification (or sometimes functional specifications) is a formal document used to describe in detail for software developers a product's intended capabilities, appearance, and interactions with users. The functional specification is a kind of guideline and continuing reference point as the developers write the programming code. (At least one major product development group used a "Write the manual first" approach. Before the product existed, they wrote the user's guide for a word processing system, then declared that the user's guide was the functional specification. The developers were challenged to create a product that matched what the user's guide described.) Typically, the functional specification for an application program with a series of interactive windows and dialogs with a user would show the visual appearance of the user interface and describe each of the possible user input actions and the program response actions. A functional specification may also contain formal descriptions of user tasks, dependencies on other products, and usability criteria. Many companies have a guide for developers that describes what topics any product's functional specification should contain.
For a sense of where the functional specification fits into the development process, here are a typical series of steps in developing a software product:
Leer más ...
// //

FAQ: SAPScripts

How do I create Boxes in SAPScript?
You can create Boxes in the SAPScript using the BOX command specifying the x,y co-ordinates and the width and the height
BOX XPOS '0' CM YPOS '0.5' CM WIDTH '9.2' CM HEIGHT '3.5' CM FRAME 8 TW.

How do I set tabs between the fields in display?
In the Paragraph Format tab, create a new paragraph format. In the "Tabs" Tab, enter the tab position and the alignment for the fields.

How do I create standard texts for the scripts?
You can create standard texts using the transaction SO10. Then to insert these standard texts in the SAPScript choose the menu, Insert->Text->Standard and choose the standard text that you want to choose.
Leer más ...
// //

Screen exit for standard trans

Introduction

SAP provides standard transactions to enter data into database. But a client may want to maintain some additional information in SAP other than what is provided.

To make provisions for this, additional screens have to be provided and additional fields must be added into appropriate database table.

Leer más ...
// //

FAQ: Client copy

Symptom

1. Which authorizations are required to execute a client copy?
2. Which data is actually copied with a client copy?
3. Can I only copy the Customizing and therefore receive the application data in the target client?
4. Can I copy between systems with different R/3 releases/add-ons?
5. Can I create client copies in a heterogeneous system landscape?
6. How can I improve the performance of a client copy?
7. Which is better or faster, a client transport or a remote copy?
8. How much space does the new client require?
9. Can I exclude certain tables from a client copy?
10. Where do I find the cause of an error or a copy termination?
11. How does a client copy behave during a termination or database error? When does the system offer a restart?
12. How do I create a new client? Which copy profile and which source client should I use?
13. Why does a remote copy terminate, referring to DDIC differences?
14. Why there are still differences between the systems, for instance with the programs, even after I copy with the copy profile SAP_ALL?
15. What is client 001 used for?
16. Can I delete client 001?
17. Can I use client 001 in production?
18. Can I use more than one client for production in a system?
19. After a client copy, there are problems with number ranges in the target client. Why is this?

Other terms

FAQ, Q+A, CC-INFO, CC_ADMIN, SCCL, SCC5, SCC7, SCC8, SCC9

Leer más ...
// //

FBL1: line item settings

FBL1 - Display Vendor Line Items - Configure the line item settings

07F4 - Choose line items selection criteria
O7Z3 - Define line layouts
O7R1 - Define total variants

Fuente.
Leer más ...
// //

FAQs: Currency translation

I. Persistence of the currency translation (Tables TCUR*)

1. How are the entries of the TCURF and TCURR tables related?
The TCURR table contains only the exchange rates for the exchange rate type, the currency pair combination, and the validity date.
It is not really a customizing table at all, but an application table that is periodically maintained.
However, the exchange rates contained in table TCURR cannot be interpreted in isolation, since they always refer to a data record in factor table TCURF.
This is necessary because the exchange rates are stored in TCURR in a fixed numerical format (4 places before the decimal point, and five decimal places after the decimal point).
This storage format allows for exchange rates between 0.00001 and 9999.99999, although there are currency pairs that have exchange rates that are greater or less than this. By selecting the appropriate exchange rate factors, the system can also display these exchange rates. In this case the system does not compare a single unit of the first currency with a single unit of the second currency; instead the system displays any order of magnitude between 1 and 100,000,000 of the first currency and compares it with a single unit of the second currency, or vice-versa.
The exchange rates in TCURR always refer to the factors contained in TCURF.
The fields FFACT and TFACT for exchange rate factors are present in table TCURR, but they are of no importance.
The factors displayed in Transaction OB08 (Maintenance view of V_TCURR for exchange rate entry) are always taken from table TCURF, and not from table TCURR.

Leer más ...
// //

Debugging a popup window

To debug a popup, create a text file on your local computer with below texts
[FUNCTION]
Command=/H
Title=Debugger
Type=SystemCommand

Place file on your desktop. To debug a popup drag and drop this file over the popup.

<source>
Leer más ...
// //

Role Comparing in SAP

For role comparison both the roles must be in the same system, in same client.
   
Transaction code SUIM -> Comparison-> Roles
   
If the roles are in different system, then transport the role into one of the system and do comparison.  If no transport connection defined then, you can use the upload and download option in the PFCG.

Steps for Role Comparing:

1. Run the t-code SUIM
   
2. Go To Comparison and select the option of roles
   
3. Click on Across systems option it will give option to select the sys name under Remote Comparison there enter the SYS ID between which system you want to do comparison and put the role name in compare role section then execute it will give you the result.
   
4. If there are any difference between then the  t-codes it will be in red color otherwise in yellow?
<source>

Leer más ...
// //

Important Tables in SAP CO

Controlling

Table Name Description Important Fields
AUSP Characteristic Values MANDT / OBJEK / ATINN / ATZHL
CO-KBAS Overhead Cost Controlling
A132 Price per Cost Center MANDT / KAPPL / KSCHL / KOKRS
A136 Price per Controlling Area MANDT / KAPPL / KSCHL / KOKRS
A137 Price per Country / Region MANDT / KAPPL / KSCHL / KOKRS
COSC CO Objects: Assignment of Origina MANDT / OBJNR / SCTYP / VERSN
CSSK Cost Center / Cost Element MANDT / VERSN / KOKRS / GJAHR
CSSL Cost Center / Activity Type MANDT / KOKRS / KOSTL / LSTAR
KAPS CO Period Locks MANDT / KOKRS / GJAHR / VERSN

CO-KBASCORE Overhead Cost Controlling: General Services
CSKA Cost Elements (Data Dependent on MANDT / KTOPL / KSTAR
CSKB Cost Elements (Data Dependent on MANDT / KOKRS / KSTAR / DATBI
CSKS Cost Center Master Data MANDT / KOKRS / KOSTL / DATBI
CSLA Activity Master MANDT / KOKRS / LSTAR / DATBI

Leer más ...
// //

Data Archiving

Data archiving removes bulk data which is no longer required in the System, but which must be retained accessibly, from the database. Data in the R/3 database can only be archived via archiving objects, which describe the data structure. Financial accounting documents, for example are archived via the archiving object FI_DOCUMNT, which comprises the document header, company-code-dependent postings, change documents, SAPscript texts and other elements. The application archiving objects are pre-defined in the system. The archiving programs are scheduled as background jobs, but can run during on-line processing. The system need not be shutdown.
Leer más ...