In J1INCHLN "MESSAGE_TYPE_X" Occured.
Dear Team,
We are in ECC 6.0 and our patch level is 6.4.
We are getting error message "MESSAGE_TYPE_X" while doing TDS Payment in J1INCHLN. There fore please suggest the solution for resolving this.
Regards / paul
goto st22, and check the whole list of shot dump content,
please use message number advised in the content , find OSS notes ,
you can find corresponding notes.
if you cannot find , please past the content here, I will help you then.
Similar Messages
-
Run-time error "MESSAGE_TYPE_X" occurred
we have this error every day in our sytem SAP PI SP19
in st22:
"MESSAGE_TYPE_X" " "
"CL_SWF_RUN_TRANSACTION_MANAGERCP" or "CL_SWF_RUN_TRANSACTION_MANAGERCM006"
"SAVE"
can anyone help me.A similar problem is discussed here...check if it helps:
Re: IDoc to File, SM58 shows error, ST22 short dump - Runtime error
Re: Runtime errors for Branched in SXMB_MONI
Re: BPM : Message scheduled on the outbound side .... check the last post in this discussion
Regards,
Abhishek. -
Hi Friends,
I was face some Interview.
Please send answers to the questions?
How many data Fields and key fields we can create in DSO?
You can overwrite key fields or Data Fields?
Which up date we use in Delta queue extraction( v1 or v2 or v3)
Which message we get when transported request is failed?
what is the Structural difference between Infoucbe and DSO
Data Loading is taking huge time when we extract data from source system to BI system/ how to solve?(Before it took 3-4 Hours now data loading takes 4 days)What is the difference between Display Attribute and
Navigational Attribute? How to make display attribute and navigational
attribute?
How to load flat file data?
How to load Hierarchy file data?
What is HACR?
How to maintain HACR?
If any issue in HACR then how to resolve the issue?
What is Baby Cube?
Why we are creating Aggregates?
What is the use of Aggregates?
Is there
any particular field on that we can create Aggregates or we can maintain
Aggregate on any field?
What is
the different DSO available? And what is the difference between those DSO?
What is
replacement path?
What are
the extractor types?
• Application Specific
o BW Content FI, HR, CO, SAP CRM, LO Cockpit
o Customer-Generated Extractors
LIS, FI-SL, CO-PA
• Cross Application (Generic Extractors)
o DB View, InfoSet, Function Module
2. What are the steps involved in LO Extraction?
• The steps are:
o RSA5 Select the DataSources
o LBWE Maintain DataSources and Activate Extract Structures
o LBWG Delete Setup Tables
o 0LI*BW Setup tables
o RSA3 Check extraction and the data in Setup tables
o LBWQ Check the extraction queue
o LBWF Log for LO Extract Structures
o RSA7 BW Delta
Queue Monitor
3. How to create a connection with LIS InfoStructures?
• LBW0 Connecting LIS InfoStructures to BW
4. What is the difference between ODS and InfoCube and MultiProvider?
• ODS: Provides granular data, allows overwrite and data is in transparent
tables, ideal for drilldown and RRI.
• CUBE: Follows the star schema, we can only append data, ideal for primary
reporting.
• MultiProvider: Does not have physical data. It allows to access data from
different InfoProviders (Cube, ODS, InfoObject). It is also preferred for
reporting.
5. What are Start routines, Transfer routines and Update routines?
• Start Routines: The start routine is run for each DataPackage after the data
has been written to the PSA and before the transfer rules have been executed.
It allows complex computations for a key figure or a characteristic. It has no
return value. Its purpose is to execute preliminary calculations and to store
them in global DataStructures. This structure or table can be accessed in the
other routines. The entire DataPackage in the transfer structure format is used
as a parameter for the routine.
• Transfer / Update Routines: They are defined at the InfoObject level. It is
like the Start Routine. It is independent of the DataSource. We can use this to
define Global Data and Global Checks.
6. What is the difference between start routine and update routine, when, how
and why are they called?
• Start routine can be used to access InfoPackage while update routines are
used while updating the Data Targets.
7. What is the table that is used in start routines?
• Always the table structure will be the structure of an ODS or InfoCube. For
example if it is an ODS then active table structure will be the table.
8. Explain how you used Start routines in your project?
• Start routines are used for mass processing of records. In start routine all
the records of DataPackage is available for processing. So we can process all
these records together in start routine. In one of scenario, we wanted to apply
size % to the forecast data. For example if material M1 is forecasted to say
100 in May. Then after applying size %(Small 20%, Medium 40%, Large 20%, Extra
Large 20%), we wanted to have 4 records against one single record that is
coming in the info package. This is achieved in start routine.
9. What are Return Tables?
• When we want to return multiple records, instead of single value, we use the
return table in the Update Routine. Example: If we have total telephone expense
for a Cost Center, using a return table we can get
expense per employee.
10. How do start routine and return table synchronize with each other?
• Return table is used to return the Value following the execution of start
routine
11. What is the difference
between V1, V2 and V3 updates?
• V1 Update: It is a Synchronous update. Here the Statistics update is carried
out at the same time as the document update (in the application
tables).
• V2 Update: It is an Asynchronous update. Statistics update and the Document
update take place as different tasks.
o V1 & V2 don't need scheduling.
• Serialized V3 Update: The V3 collective update must be scheduled as a job
(via LBWE). Here, document data is collected in the order it was created and
transferred into the BW as a batch job. The transfer sequence may not be the
same as the order in which the data was created in all scenarios. V3 update
only processes the update data that is successfully processed with the V2
update.
12. What is compression?
• It is a process used to delete the Request IDs and this saves space.
13. What is Rollup?
• This is used to load new DataPackages (requests) into the InfoCube
aggregates. If we have not performed a rollup then the new InfoCube data will
not be available while reporting on the aggregate.
14. What is table partitioning and what are the benefits of partitioning in an
InfoCube?
• It is the method of dividing a table which would enable a quick reference.
SAP uses fact file partitioning to improve performance. We can partition only
at 0CALMONTH or 0FISCPER. Table partitioning helps to run the report faster as
data is stored in the relevant partitions. Also table maintenance becomes
easier. Oracle,
Informix, IBM DB2/390 supports table partitioning while SAP DB, Microsoft SQL
Server, IBM DB2/400 do not support table portioning.
15. How many extra partitions are created and why?
• Two partitions are created for date before the begin date and after the end
date.
16. What are the options available in transfer rule?
• InfoObject
• Constant
• Routine
• Formula
17. How would you optimize the dimensions?
• We should define as many dimensions as possible and we have to take care that
no single dimension crosses more than 20% of the fact table size.
18. What are Conversion Routines for units and currencies in the update rule?
• Using this option we can write ABAP
code for Units / Currencies conversion. If we enable this flag then unit of Key
Figure appears in the ABAP code as an additional parameter. For example, we can
convert units in Pounds to Kilos.
19. Can an InfoObject be an InfoProvider, how and why?
• Yes, when we want to report on Characteristics or Master Data. We have to
right click on the InfoArea and select "Insert characteristic as data
target". For example, we can make 0CUSTOMER as an InfoProvider and report
on it.
20. What is Open Hub Service?
• The Open Hub Service enables us to distribute data from an SAP BW system into
external Data Marts, analytical applications, and other applications. We can
ensure controlled distribution using several systems. The central object for
exporting data is the InfoSpoke. We can define the source and the target object
for the data. BW becomes a hub of an enterprise data warehouse.
The distribution of data becomes clear through central monitoring from the
distribution status in the BW system.
21. How do you transform Open
Hub Data?
• Using BADI we can transform Open Hub Data according to the destination
requirement.
22. What is ODS?
• Operational DataSource is used for detailed storage of data. We can overwrite
data in the ODS. The data is stored in transparent tables.
23. What are BW Statistics and what is its use?
• They are group of Business Content InfoCubes which are used to measure
performance for Query and Load Monitoring. It also shows the usage of
aggregates, OLAP and Warehouse management
http://www.ittestpapers.com/articles/713/3/SAP-BW-Interview-Questions---Part-A/Page3.html
Communication Structure and Transfer
rules
• Create and InfoPackage
• Load Data
25. What are the delta options available when you load from flat file?
• The 3 options for Delta Management with Flat Files:
o Full Upload
o New Status for Changed records (ODS Object only)
o Additive Delta (ODS Object & InfoCube)
Q) Under which menu path is the Test Workbench to be found, including in
earlier Releases?
The menu path is: Tools - ABAP Workbench - Test - Test Workbench.
Q) I want to delete a BEx query that is in Production system through request. Is
anyone aware about it?
A) Have you tried the RSZDELETE transaction?
Q) Errors while monitoring process chains.
A) During data loading. Apart from them, in process chains you add so many
process types, for example after loading data into Info Cube, you rollup data
into aggregates, now this rolling up of data into aggregates is a process type
which you keep after the process type for loading data into Cube. This rolling
up into aggregates might fail.
Another one is after you load data into ODS, you activate ODS data (another
process type) this might also fail.
Q) In Monitor----- Details (Header/Status/Details) à Under Processing (data
packet): Everything OK à Context menu of Data Package 1 (1 Records): Everything
OK ---- Simulate update. (Here we can debug update rules or transfer rules.)
SM50 à Program/Mode à Program à Debugging & debug this work process.
Q) PSA Cleansing.
A) You know how to edit PSA. I don't think you can delete single records. You
have to delete entire PSA data for a request.
Q) Can we make a datasource to support delta.
A) If this is a custom (user-defined) datasource you can make the datasource
delta enabled. While creating datasource from RSO2, after entering datasource
name and pressing create, in the next screen there is one button at the top,
which says generic delta. If you want more details about this there is a
chapter in Extraction book, it's in last pages u find out.
Generic delta services: -
Supports delta extraction for generic extractors according to:
Time stamp
Calendar day
Numeric pointer, such as document number & counter
Only one of these attributes can be set as a delta attribute.
Delta extraction is supported for all generic extractors, such as tables/views,
SAP Query and function modules
The delta queue (RSA7) allows you to monitor the current status of the delta
attribute
Q) Workbooks, as a general rule, should be transported with the
role.
Here are a couple of scenarios:
1. If both the workbook and its role have been previously transported, then the
role does not need to be part of the transport.
2. If the role exists in both dev and the target system but the workbook has
never been transported, and then you have a choice of transporting the role
(recommended) or just the workbook. If only the workbook is transported, then
an additional step will have to be taken after import: Locate the WorkbookID
via Table RSRWBINDEXT (in Dev and verify the same exists in the target system)
and proceed to manually add it to the role in the target system via Transaction
Code PFCG -- ALWAYS use control c/control v copy/paste for manually adding!
3. If the role does not exist in the target system you should transport both
the role and workbook. Keep in mind that a workbook is an object unto itself
and has no dependencies on other objects. Thus, you do not receive an error
message from the transport of 'just a workbook' -- even though it may not be
visible, it will exist (verified via Table RSRWBINDEXT).
Overall, as a general rule, you should transport roles with workbooks.
Q) How much time does it take to extract 1 million (10 lackhs) of records into
an infocube?
A. This depends, if you have complex coding in update rules it will take longer
time, or else it will take less than 30 minutes.
Q) What are the five ASAP Methodologies?
A: Project plan, Business Blue print, Realization, Final preparation & Go-Live - support.
1. Project Preparation: In this phase, decision makers define clear project
objectives and an efficient decision making process ( i.e. Discussions with the
client, like what are his needs and requirements etc.). Project managers
will be involved in this phase (I guess).
A Project Charter is issued and an implementation strategy is outlined in this
phase.
2. Business Blueprint: It is a detailed documentation of your company's
requirements. (i.e. what are the objects we need to develop are modified
depending on the client's requirements).
3. Realization: In this only, the implementation of the project takes place (development
of objects etc) and we are involved in the project from here only.
4. Final Preparation: Final preparation before going live i.e. testing,
conducting pre-go-live, end user training etc.
End user training is given that is in the client site you train them how to
work with the new environment, as they are new to the technology.
5. Go-Live & support: The project has gone live and it is into production.
The Project team will be supporting the end users.
Q) What is landscape of R/3 & what is landscape of BW. Landscape of R/3 not
sure.
Then Landscape of b/w: u have the development system, testing system, production system
Development system: All the implementation part is done in this sys. (I.e.,
Analysis of objects developing, modification etc) and from here the objects are
transported to the testing system, but before transporting an initial test
known as Unit testing
(testing of objects) is done in the development sys.
Testing/Quality system: quality check is done in this system and integration
testing is done.
Production system: All the extraction part takes place in this sys.
Q) How do you measure the size of infocube?
A: In no of records.
Q). Difference between infocube and ODS?
A: Infocube is structured as star schema (extended) where a fact table is
surrounded by different dim table that are linked with DIM'ids. And the data
wise, you will have aggregated data in the cubes. No overwrite functionality
ODS is a flat structure (flat table) with no star schema concept and which will
have granular data (detailed level). Overwrite functionality.
Flat file
datasources does not support 0recordmode in extraction.
x before, -after, n new, a add, d delete, r reverse
Q) Difference between display attributes and navigational attributes?
A: Display attribute is one, which is used only for display purpose in the
report. Where as navigational attribute is used for drilling down in the
report. We don't need to maintain Navigational attribute in the cube as a
characteristic (that is the advantage) to drill down.
Q. SOME DATA IS UPLOADED TWICE INTO INFOCUBE. HOW TO CORRECT IT?
A: But how is it possible? If you load it manually twice, then you can delete
it by requestID.
Q. CAN U ADD A NEW FIELD AT THE ODS LEVEL?
Sure you can. ODS is nothing but a table.
Q. CAN NUMBER OF DATASOURCES HAVE ONE INFOSOURCE?
A) Yes of course. For example, for loading text and hierarchies we use
different data sources but the same InfoSource.
Q. BRIEF THE DATAFLOW IN BW.
A) Data flows from transactional system to analytical system (BW). DataSources
on the transactional system needs to be replicated on BW side and attached to
infosource and update rules respectively.
Q. CURRENCY CONVERSIONS CAN BE WRITTEN IN UPDATE RULES. WHY NOT IN TRANSFER
RULES?
Q) WHAT IS PROCEDURE TO UPDATE DATA INTO DATA TARGETS?
FULL and DELTA.
Q) AS WE USE Sbwnn, sbiw1, sbiw2 for delta update in LIS THEN
WHAT IS THE PROCEDURE IN LO-COCKPIT?
No LIS in LO cockpit. We will have datasources and can be maintained (append
fields). Refer white paper
on LO-Cockpit extractions.
Q) Why we delete the setup tables (LBWG) & fill them (OLI*BW)?
A) Initially we don't delete the setup tables but when we do change in extract
structure we go for it. We r changing the extract structure right, that means
there are some newly added fields in that which r not before. So to get the
required data ( i.e.; the data which is required is taken and to avoid
redundancy) we delete n then fill the setup tables.
To refresh the statistical data.
The extraction set up reads the dataset that you want to process such as,
customers orders with the tables like VBAK, VBAP) & fills the relevant communication
structure with the data. The data is stored in cluster
tables from where it is read when the initialization is run. It is important
that during initialization phase, no one generates or modifies application
data, at least until the tables can be set up.
Q) SIGNIFICANCE of ODS?
It holds granular data (detailed level).
Q) WHERE THE PSA DATA IS STORED?
In PSA table.
Q) WHAT IS DATA SIZE?
The volume of data one data target holds (in no. of records)
Q) Different types of INFOCUBES.
Basic, Virtual (remote, sap remote and multi)
Virtual Cube is used for example, if you consider railways reservation all the
information has to be updated online. For designing the Virtual cube you have
to write the function module that is linking to table, Virtual cube it is like
a the structure, when ever the table is updated the virtual cube will fetch the
data from table and display report Online... FYI.. you will get the information
: https://www.sdn.sap.com/sdn
/index.sdn and search for Designing Virtual Cube and you will get
a good material designing the Function Module
Q) INFOSET QUERY.
Can be made of ODS's and Characteristic InfoObjects with masterdata.
Q) IF THERE ARE 2 DATASOURCES HOW MANY TRANSFER STRUCTURES ARE THERE.
In R/3 or in BW? 2 in R/3 and 2 in BW
Q) ROUTINES?
Exist in the InfoObject, transfer routines, update routines and start routine
Q) BRIEF SOME STRUCTURES USED IN BEX.
Rows and Columns, you can create structures.
Q) WHAT ARE THE DIFFERENT VARIABLES USED IN BEX?
Different Variable's are Texts, Formulas, Hierarchies, Hierarchy nodes &
Characteristic values.
Variable Types are
Manual entry /default value
Replacement path
SAP exit
Customer exit
Authorization
Q) HOW MANY LEVELS YOU CAN GO IN REPORTING?
You can drill down to any level by using Navigational attributes and jump
targets.
Q) WHAT ARE INDEXES?
Indexes are data base indexes, which help in retrieving data fastly.
Q) DIFFERENCE BETWEEN 2.1 AND 3.X VERSIONS.
Help! Refer documentation
Q) IS IT NESSESARY TO INITIALIZE EACH TIME THE DELTA UPDATE IS USED?
No.
Q) WHAT IS THE SIGNIFICANCE OF KPI'S?
KPI's indicate the performance of a company. These are key figures
Q) AFTER THE DATA EXTRACTION
WHAT IS THE IMAGE POSITION.
After image (correct me if I am wrong)
Q) REPORTING AND RESTRICTIONS.
Help! Refer documentation.
Q) TOOLS USED FOR PERFORMANCE TUNING.
ST22, Number ranges, delete indexes before load. Etc
Q) PROCESS CHAINS: IF U has USED IT THEN HOW WILL U SCHEDULING DATA DAILY.
There should be some tool to run the job daily (SM37 jobs)
Q) AUTHORIZATIONS.
Profile generator
Q) WEB REPORTING.
What are you expecting??
Q) CAN CHARECTERSTIC INFOOBJECT CAN BE INFOPROVIDER.
Of course
Q) PROCEDURES OF REPORTING ON MULTICUBES
Refer help. What are you expecting? MultiCube works on Union condition
Q) EXPLAIN TRANPSORTATION OF OBJECTS?
Dev---àQ and Dev-------àP
Q) What types of partitioning are there for BW?
There are two Partitioning Performance aspects for BW (Cube & PSA)
Query Data Retrieval
Performance Improvement:
Partitioning by (say) Date Range improves data retrieval by making best use of
database [data range] execution plans and indexes (of say Oracle database engine).
B) Transactional Load Partitioning Improvement:
Partitioning based on expected load volumes and data element sizes. Improves
data loading into PSA and Cubes by infopackages (Eg. without timeouts).
Q) How can I compare data in R/3 with data in a BW Cube after the daily delta
loads? Are there any standard procedures for checking them or matching the
number of records?
A) You can go to R/3 TCode RSA3 and run the extractor. It will give you the
number of records extracted. Then go to BW Monitor to check the number of
records in the PSA and check to see if it is the same & also in the monitor
header tab.
A) RSA3 is a simple extractor checker program that allows you to rule out
extracts problems in R/3. It is simple to use, but only really tells you if the
extractor works. Since records that get updated into Cubes/ODS structures are
controlled by Update Rules, you will not be able to determine what is in the
Cube compared to what is in the R/3 environment. You will need to compare
records on a 1:1 basis against records in R/3 transactions for the functional
area in question. I would recommend enlisting the help of the end user community
to assist since they presumably know the data.
To use RSA3, go to it and enter the extractor ex: 2LIS_02_HDR. Click execute
and you will see the record count, you can also go to display that data. You
are not modifying anything so what you do in RSA3 has no effect on data quality
afterwards. However, it will not tell you how many records should be expected
in BW for a given load. You have that information in the monitor RSMO during
and after data loads. From RSMO for a given load you can determine how many
records were passed through the transfer rules from R/3, how many targets were
updated, and how many records passed through the Update Rules. It also gives
you error messages from the PSA.
Q) Types of Transfer Rules?
A) Field to Field mapping, Constant, Variable & routine.
Q) Types of Update Rules?
A) (Check box), Return table
Q) Transfer Routine?
A) Routines, which we write in, transfer rules.
Q) Update Routine?
A) Routines, which we write in Update rules
Q) What is the difference between writing a routine in transfer rules and
writing a routine in update rules?
A) If you are using the same InfoSource to update data in more than one data
target its better u write in transfer rules because u can assign one InfoSource
to more than one data target & and what ever logic u write in update rules
it is specific to particular one data target.
Q) Routine with Return Table.
A) Update rules generally only have one return value. However, you can create a
routine in the tab strip key figure calculation, by choosing checkbox Return
table. The corresponding key figure routine then no longer has a return value,
but a return table. You can then generate as many key figure values, as you
like from one data record.
Q) Start routines?
A) Start routines u can write in both updates rules and transfer rules, suppose
you want to restrict (delete) some records based on conditions before getting
loaded into data targets, then you can specify this in update rules-start
routine.
Ex: - Delete Data_Package ani ante it will delete a record based on the
condition
Q) X & Y Tables?
X-table = A table to link material SIDs with SIDs for time-independent
navigation attributes.
Y-table = A table to link material SIDs with SIDS for time-dependent navigation
attributes.
There are four types of sid tables
X time independent navigational attributes sid tables
Y time dependent navigational attributes sid tables
H hierarchy sid tables
I hierarchy structure sid tables
Q) Filters & Restricted Key figures (real time example)
Restricted KF's u can have for an SD cube: billed quantity, billing value, no:
of billing documents as RKF's.
Q) Line-Item Dimension (give me an real time example)
Line-Item Dimension: Invoice no: or Doc no: is a real time example
Q) What does the number in the 'Total' column in Transaction RSA7 mean?
A) The 'Total' column displays the number of LUWs that were written in the
delta queue and that have not yet been confirmed. The number includes the LUWs
of the last delta request (for repetition of a delta request) and the LUWs for
the next delta request. A LUW only disappears from the RSA7 display when it has
been transferred to the BW System and a new delta request has been received
from the BW System.
Q) How to know in which table (SAP BW) contains Technical Name / Description
and creation data of a particular Reports. Reports that are created using BEx
Analyzer.
A) There is no such table in BW if you want to know such details while you are
opening a particular query press properties button you will come to know all
the details that you wanted.
You will find your information about technical names and description about
queries in the following tables. Directory of all reports (Table RSRREPDIR) and
Directory of the reporting component elements (Table RSZELTDIR) for workbooks
and the connections to queries check Where- used list for reports in workbooks
(Table RSRWORKBOOK) Titles of Excel Workbooks in InfoCatalog (Table
RSRWBINDEXT)
Q) What is a LUW in the delta queue?
A) A LUW from the point of view of the delta queue can be an individual
document, a group of documents from a collective run or a whole data packet of
an application
extractor.
Q) Why does the number in the 'Total' column in the overview screen of
Transaction RSA7 differ from the number of data records that is displayed when
you call the detail view?
A) The number on the overview screen corresponds to the total of LUWs (see also
first question) that were written to the qRFC queue and that have not yet been
confirmed. The detail screen displays the records contained in the LUWs. Both,
the records belonging to the previous delta request and the records that do not
meet the selection conditions of the preceding delta init requests are filtered
out. Thus, only the records that are ready for the next delta request are
displayed on the detail screen. In the detail screen of Transaction RSA7, a
possibly existing customer exit is not taken into account.
Q) Why does Transaction RSA7 still display LUWs on the overview screen after
successful delta loading?
A) Only when a new delta has been requested does the source system learn that
the previous delta was successfully loaded to the BW System. Then, the LUWs of
the previous delta may be confirmed (and also deleted). In the meantime, the
LUWs must be kept for a possible delta request repetition. In particular, the
number on the overview screen does not change when the first delta was loaded
to the BW System.
Q) Why are selections not taken into account when the delta queue is filled?
A) Filtering according to selections takes place when the system reads from the
delta queue. This is necessary for reasons of performance.
Q) Why is there a DataSource with '0' records in RSA7 if delta exists and has
also been loaded successfully?
It is most likely that this is a DataSource that does not send delta data to
the BW System via the delta queue but directly via the extractor (delta for
master data using ALE change pointers). Such a DataSource should not be
displayed in RSA7. This error is corrected with BW 2.0B Support Package 11.
Q) Do the entries in table ROIDOCPRMS have an impact on the performance of the
loading procedure from the delta queue?
A) The impact is limited. If performance problems are related to the loading
process from the delta queue, then refer to the application-specific notes (for
example in the CO-PA area, in the logistics cockpit area and so on).
Caution: As of Plug In 2000.2 patch 3 the entries in table ROIDOCPRMS are as
effective for the delta queue as for a full update. Please note, however, that
LUWs are not split during data loading for consistency reasons. This means that
when very large LUWs are written to the DeltaQueue, the actual package size may
differ considerably from the MAXSIZE and MAXLINES parameters.
Q) Why does it take so long to display the data in the delta queue (for example
approximately 2 hours)?
A) With Plug In 2001.1 the display was changed: the user has the option of
defining the amount of data to be displayed, to restrict it, to selectively
choose the number of a data record, to make a distinction between the 'actual'
delta data and the data intended for repetition and so on.
Q) What is the purpose of function 'Delete data and meta data in a queue' in
RSA7? What exactly is deleted?
A) You should act with extreme caution when you use the deletion function in
the delta queue. It is comparable to deleting an InitDelta in the BW System and
should preferably be executed there. You do not only delete all data of this
DataSource for the affected BW System, but also lose the entire information
concerning the delta initialization. Then you can only request new deltas after
another delta initialization.
When you delete the data, the LUWs kept in the qRFC queue for the corresponding
target system are confirmed. Physical deletion only takes place in the qRFC
outbound queue if there are no more references to the LUWs.
The deletion function is for example intended for a case where the BW System,
from which the delta initialization was originally executed, no longer exists
or can no longer be accessed.
Q) Why does it take so long to delete from the delta queue (for example half a
day)?
A) Import PlugIn 2000.2 patch 3. With this patch the performance during
deletion is considerably improved.
Q) Why is the delta queue not updated when you start the V3 update in the
logistics cockpit area?
A) It is most likely that a delta initialization had not yet run or that the
delta initialization was not successful. A successful delta initialization (the
corresponding request must have QM status 'green' in the BW System) is a
prerequisite for the application data being written in the delta queue.
Q) What is the relationship between RSA7 and the qRFC monitor (Transaction
SMQ1)?
A) The qRFC monitor basically displays the same data as RSA7. The internal
queue name must be used for selection on the initial screen of the qRFC
monitor. This is made up of the prefix 'BW, the client and the short name of
the DataSource. For DataSources whose name are 19 characters long or shorter,
the short name corresponds to the name of the DataSource. For DataSources whose
name is longer than 19 characters (for delta-capable DataSources only possible
as of PlugIn 2001.1) the short name is assigned in table ROOSSHORTN.
In the qRFC monitor you cannot distinguish between repeatable and new LUWs.
Moreover, the data of a LUW is displayed in an unstructured manner there.
Q) Why are the data in the delta queue although the V3 update was not started?
A) Data was posted in background. Then, the records are updated directly in the
delta queue (RSA7). This happens in particular during automatic goods receipt
posting (MRRS). There is no duplicate transfer of records to the BW system. See
Note 417189.
Q) Why does button 'Repeatable' on the RSA7 data details screen not only show
data loaded into BW during the last delta but also data that were newly added,
i.e. 'pure' delta records?
A) Was programmed in a way that the request in repeat mode fetches both
actually repeatable (old) data and new data from the source system.
Q) I loaded several delta inits with various selections. For which one is the
delta loaded?
A) For delta, all selections made via delta inits are summed up. This means, a
delta for the 'total' of all delta initializations is loaded.
Q) How many selections for delta inits are possible in the system?
A) With simple selections (intervals without complicated join conditions or
single values), you can make up to about 100 delta inits. It should not be
more.
With complicated selection conditions, it should be only up to 10-20 delta
inits.
Reason: With many selection conditions that are joined in a complicated way,
too many 'where' lines are generated in the generated ABAP
source code that may exceed the memory limit.
Q) I intend to copy the source system, i.e. make a client copy. What will
happen with may delta? Should I initialize again after that?
A) Before you copy a source client or source system, make sure that your deltas
have been fetched from the DeltaQueue into BW and that no delta is pending.
After the client copy, an inconsistency might occur between BW delta tables and
the OLTP delta tables as described in Note 405943. After the client copy, Table
ROOSPRMSC will probably be empty in the OLTP since this table is
client-independent. After the system copy, the table will contain the entries
with the old logical system name that are no longer useful for further delta
loading from the new logical system. The delta must be initialized in any case
since delta depends on both the BW system and the source system. Even if no
dump 'MESSAGE_TYPE_X' occurs in BW when editing or creating an InfoPackage, you
should expect that the delta have to be initialized after the copy.
Q) Is it allowed in Transaction SMQ1 to use the functions for manual control of
processes?
A) Use SMQ1 as an instrument for diagnosis and control only. Make changes to BW
queues only after informing the BW Support or only if this is explicitly
requested in a note for component 'BC-BW' or 'BW-WHM-SAPI'.
Q) Despite of the delta request being started after completion of the
collective run (V3 update), it does not contain all documents. Only another
delta request loads the missing documents into BW. What is the cause for this
"splitting"?
A) The collective run submits the open V2 documents for processing to the task
handler, which processes them in one or several parallel update processes in an
asynchronous way. For this reason, plan a sufficiently large "safety time
window" between the end of the collective run in the source system and the
start of the delta request in BW. An alternative solution where this problem
does not occur is described in Note 505700.
Q) Despite my deleting the delta init, LUWs are still written into the
DeltaQueue?
A) In general, delta initializations and deletions of delta inits should always
be carried out at a time when no posting takes place. Otherwise, buffer
problems may occur: If a user started the internal mode at a time when the
delta initialization was still active, he/she posts data into the queue even
though the initialization had been deleted in the meantime. This is the case in
your system.
Q) In SMQ1 (qRFC Monitor) I have status 'NOSEND'. In the table TRFCQOUT, some
entries have the status 'READY', others 'RECORDED'. ARFCSSTATE is 'READ'. What
do these statuses mean? Which values in the field 'Status' mean what and which
values are correct and which are alarming? Are the statuses BW-specific or
generally valid in qRFC?
A) Table TRFCQOUT and ARFCSSTATE: Status READ means that the record was read
once either in a delta request or in a repetition of the delta request.
However, this does not mean that the record has successfully reached the BW
yet. The status READY in the TRFCQOUT and RECORDED in the ARFCSSTATE means that
the record has been written into the DeltaQueue and will be loaded into the BW
with the next delta request or a repetition of a delta. In any case only the
statuses READ, READY and RECORDED in both tables are considered to be valid.
The status EXECUTED in TRFCQOUT can occur temporarily. It is set before
starting a DeltaExtraction for all records with status READ present at that
time. The records with status EXECUTED are usually deleted from the queue in
packages within a delta request directly after setting the status before
extracting a new delta. If you see such records, it means that either a process
which is confirming and deleting records which have been loaded into the BW is
successfully running at the moment, or, if the records remain in the table for
a longer period of time with status EXECUTED, it is likely that there are
problems with deleting the records which have already been successfully been
loaded into the BW. In this state, no more deltas are loaded into the BW. Every
other status is an indicator for an error or an inconsistency. NOSEND in SMQ1
means nothing (see note 378903).
The value 'U' in field 'NOSEND' of table TRFCQOUT is discomforting.
Q) The extract structure was changed when the DeltaQueue was empty. Afterwards
new delta records were written to the DeltaQueue. When loading the delta into
the PSA, it shows that some fields were moved. The same result occurs when the
contents of the DeltaQueue are listed via the detail display. Why are the data
displayed differently? What can be done?
Make sure that the change of the extract structure is also reflected in the
database and that all servers are synchronized. We recommend to reset the
buffers using Transaction $SYNC. If the extract structure change is not
communicated synchronously to the server where delta records are being created,
the records are written with the old structure until the new structure has been
generated. This may have disastrous consequences for the delta.
When the problem occurs, the delta needs to be re-initialized.
Q) How and where can I control whether a repeat delta is requested?
A) Via the status of the last delta in the BW Request Monitor. If the request
is RED, the next load will be of type 'Repeat'. If you need to repeat the last
load for certain reasons, set the request in the monitor to red manually. For
the contents of the repeat see Question 14. Delta requests set to red despite
of data being already updated lead to duplicate records in a subsequent repeat,
if they have not been deleted from the data targets concerned before.
Q) As of PI 2003.1, the Logistic Cockpit offers various types of update
methods. Which update method is recommended in logistics? According to which
criteria should the decision be made? How can I choose an update method in
logistics?
See the recommendation in Note 505700.
Q) Are there particular recommendations regarding the data volume the
DeltaQueue may grow to without facing the danger of a read failure due to
memory problems?
A) There is no strict limit (except for the restricted number range of the
24-digit QCOUNT counter in the LUW management table - which is of no practical
importance, however - or the restrictions regarding the volume and number of
records in a database table).
When estimating "smooth" limits, both the number of LUWs is important
and the average data volume per LUW. As a rule, we recommend to bundle data
(usually documents) already when writing to the DeltaQueue to keep number of
LUWs small (partly this can be set in the applications, e.g. in the Logistics
Cockpit). The data volume of a single LUW should not be considerably larger
than 10% of the memory available to the work process for data extraction
(in a 32-bit architecture with a memory volume of about 1GByte per work
process, 100 Mbytes per LUW should not be exceeded). That limit is of rather
small practical importance as well since a comparable limit already applies
when writing to the DeltaQueue. If the limit is observed, correct reading is
guaranteed in most cases.
If the number of LUWs cannot be reduced by bundling application transactions,
you should at least make sure that the data are fetched from all connected BWs
as quickly as possible. But for other, BW-specific, reasons, the frequency
should not be higher than one DeltaRequest per hour.
To avoid memory problems, a program-internal limit ensures that never more than
1 million LUWs are read and fetched from the database per DeltaRequest. If this
limit is reached within a request, the DeltaQueue must be emptied by several
successive DeltaRequests. We recommend, however, to try not to reach that limit
but trigger the fetching of data from the connected BWs already when the number
of LUWs reaches a 5-digit value.
Q) I would like to display the date the data was uploaded on the
report. Usually, we load the transactional data nightly. Is there any easy way
to include this information on the report for users? So that they know the
validity of the report.
A) If I understand your requirement correctly, you want to display the date on
which data was loaded into the data target from which the report is being
executed. If it is so, configure your workbook to display the text elements in
the report. This displays the relevance of data field, which is the date on which
the data load has taken place.
Q) Can we filter the fields at Transfer Structure?
Q) Can we load data directly into infoobject with out extraction is it
possible.
Yes. We can copy from other infoobject if it is same. We load data from PSA if
it is already in PSA.
Q) HOW MANY DAYS CAN WE KEEP THE DATA IN PSA, IF WE R SHEDULED DAILY, WEEKLY
AND MONTHLY.
a) We can set the time.
Q) HOW CAN U GET THE DATA FROM CLIENT IF U R WORKING ON OFFSHORE PROJECTS.
THROUGH WHICH NETWORK.
a) VPN…………….Virtual
Private Network, VPN is nothing but one sort of network
where we can connect to the client systems sitting in offshore through RAS
(Remote access server).
Q) HOW CAN U ANALIZE THE PROJECT AT FIRST?
Prepare Project Plan and Environment
Define Project Management
Standards and
Procedures
Define Implementation Standards and Procedures
Testing & Go-live + supporting.
Q) THERE is one ODS AND 4 INFOCUBES. WE SEND DATA AT TIME TO ALL CUBES IF ONE
CUBE GOT LOCK ERROR. HOW CAN U RECTIFY THE ERROR?
Go to TCode sm66 then see which one is locked select that pid from there and
goto sm12
TCode then unlock it this is happened when lock errors are occurred when u
scheduled.
Q) Can anybody tell me how to add a navigational attribute in the BEx report in
the rows?
A) Expand dimension under left side panel (that is infocube panel) select than
navigational attributes drag and drop under rows panel.
Q) IF ANY TRASACTION CODE LIKE SMPT OR STMT.
In current systems (BW 3.0B and R/3 4.6B) these Tcodes don't exist!
Q) WHAT IS TRANSACTIONAL CUBE?
A) Transactional InfoCubes differ from standard InfoCubes in that the former
have an improved write access performance level. Standard InfoCubes are
technically optimized for read-only access and for a comparatively small number
of simultaneous accesses. Instead, the transactional InfoCube was developed to
meet the demands of SAP Strategic Enterprise Management (SEM), meaning that,
data is written to the InfoCube (possibly by several users at the same time)
and re-read as soon as possible. Standard Basic cubes are not suitable for
this.
Q) Is there any way to delete cube contents within update rules from an ODS
data source? The reason for this would be to delete (or zero out) a cube record
in an "Open Order" cube if the open order quantity was 0.
I've tried using the 0recordmode but that doesn't work. Also, would it
be easier to write a program that would be run after the load and delete
the records with a zero open qty?
A) START routine for update rules u can write ABAP code.
A) Yap, you can do it. Create a start routine in Update rule.
It is not "Deleting cube contents with update rules" It is only
possible to avoid that some content is updated into the InfoCube using the
start routine. Loop at all the records and delete the record that has the
condition. "If the open order quantity was 0" You have to think also
in before and after images in case of a delta upload. In that case you may
delete the change record and keep the old and after the change the wrong
information.
Q) I am not able to access a node in hierarchy directly using variables for
reports. When I am using Tcode RSZV it is giving a message that it doesn't
exist in BW 3.0 and it is embedded in BEx. Can any one tell me the other
options to get the same functionality in BEx?
A) Tcode RSZV is used in the earlier version of 3.0B only. From 3.0B onwards,
it's possible in the Query Designer (BEx) itself. Just right click on the
InfoObject for which you want to use as variables and precede further selecting
variable type and proce -
ABAP Dump while Changing the Layout fields in Report output - RCOPCA02
Hi,
I Copied the Standard Program RCOPCA02 to ZRCOPCA02. I added two new fields(AUART, AUGRU) in the report output. It is executing correctly with default layout, While Changing the layout for displaying new fields it is dumping.
I am not understanding, What should i do...
Here is the Code.
report ZRCOPCA02 no standard page heading message-id km
line-count (2) line-size 81.
type-pools: slis, ecarc.
DDIC-Tabellen *******************************************************
tables: glpca, "Einzelposten / Ist
glu1, "Übergabestruktur FI-SL-Anzeige
t000,
tka01,
sscrfields,
vbak.
Variablen und int. Tabellen *****************************************
data: l_vbeln like vbak-vbeln,
l_auart like vbak-auart,
l_augru like vbak-augru.
data: afield type slis_fieldcat_alv,
sp_group type slis_sp_group_alv,
t_listheader type slis_t_listheader with header line,
t_layout type slis_layout_alv,
t_fieldcat type slis_t_fieldcat_alv,
t_spec_groups type slis_t_sp_group_alv,
event type slis_alv_event,
t_events type slis_t_event,
g_variant like disvariant,
gx_variant like disvariant,
g_exit(1) type c,
g_save(1) type c,
g_repid like sy-repid,
msgtyp like sy-msgty,
lt_dynpread like dynpread occurs 1 with header line,
ls_rpcak like rpcak, "note 0310592
packsize type i value 1000,
text1(60) type c,
text2(60) type c,
oldkokrs like glpca-kokrs,
oldracct like glpca-racct.
data: whr_size type i value 50,"Maximum of single values per MIC 46a
"charact. in the where-clause of the select-statement
lines type i, "number of lines of range table MIC 46a
cnt_rldnr type i, "Zähler Anzahl selektierter Ledger
cnt_kokrs type i, "Zähler Anzahl selektierter KoReKreise
cnt_poper type i, "Zähler Anzahl selektierter Perioden
cnt_ryear type i, "Zähler Anzahl selektierter GeschJahre
cnt_rvers type i, "Zähler Anzahl selektierter Versionen
cnt_bukrs type i, "Zähler Anzahl selektierter BuKreise
empge like dkobr-empge,
ksl_curr like tka01-pcacur,
hsl_curr like t001-waers,
a_rec like rstirec.
data: begin of dim_data.
include structure rgcdi. "data for dimensions
data: end of dim_data.
data: begin of tab_fields occurs 80,
name like dntab-fieldname, "fields in table i_glpca
end of tab_fields.
data: begin of i_glpca occurs 0.
include structure rpca2.
data: racct_ktext like rpcak-ktext,
psppp like prps-posid,
v_auart like vbak-auart,
v_augru like vbak-augru,
end of i_glpca.
data: rw_subrc like sy-subrc, "Flag: Report-Writer-Schnittstelle
re_subrc like sy-subrc, "Flag: Recherche-Schnittstelle
subrc like sy-subrc.
data: set_id like sethier-setid, "Set-ID "RDI_SETS_4.0
set_class like sethier-setclass, "Setklasse "RDI_SETS_4.0
set_sname like sethier-shortname."Setname (24) "RDI_SETS_4.0
data: authorised(1),
s_message(1),
auth_dbcount like sy-tabix,
Hex-Konstanten für Minimum/Maximum-Werte
begin of hex00,
x1(12) type c,
x2(12) type c,
end of hex00,
begin of hexff,
x1(12) type c,
x2(12) type c,
end of hexff.
ranges rclnt for glpca-rclnt.
field-symbols: type ecarc_glpca_curr.
Selektionsoptionen *************************************************
select-options:
rldnr for glpca-rldnr default '8A' no-display,
rassc for glpca-rassc no-display,
rrcty for glpca-rrcty default 0,
rrcty for glpca-rrcty,
rvers for glpca-rvers default '000',
kokrs for glpca-kokrs memory id cac,
bukrs for glpca-rbukrs memory id buk,
poper for glpca-poper default sy-datlo+4(2),
ryear for glpca-ryear default sy-datlo,
poper for glpca-poper,
ryear for glpca-ryear,
prctr for glpca-rprctr matchcode object prct,
pprctr for glpca-sprctr matchcode object prct,
RACCT FOR GLPCA-RACCT MATCHCODE OBJECT KART, "RD_P30K128304
racct for glpca-racct, "RD_P30K128304
drcrk for glpca-drcrk,
activ for glpca-activ,
rhoart for glpca-rhoart,
rfarea for glpca-rfarea,
stagr for glpca-stagr,
rtcur for glpca-rtcur,
runit for glpca-runit,
versa for glpca-versa no-display,
eprctr for glpca-eprctr no-display,
afabe for glpca-afabe no-display,
rmvct for glpca-rmvct no-display,
hrkft for glpca-hrkft no-display, "note 550972
sbukrs for glpca-sbukrs no-display, "note 550972
shoart for glpca-shoart no-display, "note 550972
sfarea for glpca-sfarea no-display, "note 550972
docct for glpca-docct,
docnr for glpca-docnr,
refdocct for glpca-refdocct,
refdocnr for glpca-refdocnr,
werks for glpca-werks,
repmatnr for glpca-rep_matnr matchcode object pca_shlp_rep_matnr,
rscope for glpca-rscope.
parameters: no_rrint no-display default ' '." skip "MICP40K066037
" report-report-interface
display variant ">>MICP40K039857
selection-screen begin of block 0 with frame title text-e01.
parameters: p_vari like disvariant-variant.
selection-screen comment 47(40) varname for field p_vari.
selection-screen end of block 0.
parameters log_grp(4) type c no-display default 'KE5Z'.
"<<MICP40K039857
ranges: v_racct for glpca-racct,
v_prctr for glpca-rprctr,
v_pprctr for glpca-sprctr.
Tabelle mit Werten aus den Berichts-Set vom Report-Writer *
data begin of val_tab occurs 50.
include structure rgciv.
data end of val_tab.
MICP30K166368
feldkatalog und interface für bb-schnittstelle rw MICP30K166368
MICP30K166368
"MICP30K166368
data begin of bbs_fieldtab occurs 20. "MICP30K166368
include structure rstifields. "MICP30K166368
data end of bbs_fieldtab. "MICP30K166368
archiv
type-pools: rsds.
types: begin of ty_archive_objects,
object like arch_obj-object,
end of ty_archive_objects,
ty_t_archive_objects type ty_archive_objects occurs 2.
constants: lc_set type c value 'X',
lc_report type progname value 'KE5Z',
lc_reporttype type reporttype value 'TR'.
tables: admi_files.
select-options lr_files for admi_files-archiv_key no-display.
parameter: read_db type c default 'X' no-display,
read_ar type c no-display,
arc_obj like arch_obj-object no-display,
read_as type c default 'X' no-display.
data : lt_arch_obj type ty_t_archive_objects with header line,
ls_selections type rsds_frange,
lt_selections type rsds_frange_t,
ls_selopt type rsdsselopt,
lt_glpca_archiv type ecarc_t_glpca_curr.
*********************************************************>>MICP40K039857
INITIALIZATION
initialization.
Diverse Initialisierungen
perform init_vars.
g_repid = sy-repid.
Set default values for record type
rrcty-sign = 'I'.
rrcty-option = 'EQ'.
rrcty-low = '0'.
append rrcty.
rrcty-low = '2'.
append rrcty.
Set default values for period and year (if kokrs or bukrs is known)
get parameter id 'BUK' field bukrs-low.
get parameter id 'CAC' field kokrs-low.
if kokrs-low is initial "get contr. area from company code
and not bukrs-low is initial.
call function 'KOKRS_GET_FROM_BUKRS'
exporting
i_bukrs = bukrs-low
importing
e_kokrs = kokrs-low
exceptions
no_kokrs_found = 1
others = 2.
if sy-subrc <> 0.
clear kokrs-low.
endif.
endif.
if not kokrs-low is initial.
call function 'K_KOKRS_READ' "get fiscal year variant
exporting
kokrs = kokrs-low
importing
e_tka01 = tka01
exceptions
not_found = 1
not_found_gjahr = 2
others = 3.
if sy-subrc = 0.
call function 'G_PERIOD_GET'
exporting
date = sy-datlo
variant = tka01-lmona
importing
period = poper-low
year = ryear-low
exceptions
ledger_not_assigned_to_company = 1
period_not_defined = 2
variant_not_defined = 3
others = 4.
if sy-subrc = 0.
poper-sign = 'I'.
poper-option = 'EQ'.
append poper.
ryear-sign = 'I'.
ryear-option = 'EQ'.
append ryear.
endif.
endif.
endif.
Settings for display variants
g_save = 'A'. "Schalter Varianten benutz./allg. speichern
clear g_variant.
g_variant-report = g_repid.
g_variant-log_group = log_grp.
g_variant-username = sy-uname.
Get default variant
gx_variant = g_variant.
call function 'REUSE_ALV_VARIANT_DEFAULT_GET'
exporting
i_save = g_save
changing
cs_variant = gx_variant
exceptions
not_found = 2.
if sy-subrc = 0.
p_vari = gx_variant-variant.
endif.
Set variant
if p_vari is initial.
p_vari = '1SAP'.
move p_vari to gx_variant-variant.
call function 'REUSE_ALV_VARIANT_EXISTENCE'
exporting
i_save = g_save
changing
cs_variant = gx_variant
exceptions
not_found = 1.
if sy-subrc ne 0.
clear p_vari.
clear gx_variant-variant.
endif.
endif.
varname = gx_variant-text.
"<<MICP40K039857
archiv
call function 'KARL_DATA_INPUT_INIT'
exporting
i_report = lc_report
i_reporttype = lc_reporttype
importing
e_xusedb = read_db
e_xusear = read_ar
e_archobj = arc_obj
e_infosys = read_as
tables
t_arch_sel = lr_files.
data: lt_excluding like sy-ucomm occurs 0 with header line.
call function 'RS_SET_SELSCREEN_STATUS'
exporting
p_status = 'SELSCREEN'
p_program = 'RCOPCA02'
tables
p_exclude = lt_excluding.
Initialisieren der Bericht/Bericht-Schnittstellen *
data: ld_no_rrint type boole_d. "note 490484 begin
import rri = ld_no_rrint from memory id 'RCOPCA02_NO_RRI'.
if ld_no_rrint = 'X'.
free memory id 'RCOPCA02_NO_RRI'.
else. "note 490484 end
call function 'G_REPORT_INTERFACE_INIT' "Report-Writer?
exporting "MICP30K166368
table = 'GLPCT' "MICP30K166368
importing
subrc = rw_subrc "MICP30K166368
tables "MICP30K166368
it_fieldr = bbs_fieldtab. "MICP30K166368
call function 'RSTI_APPL_STACK_POP'"oder Recherche?
importing
i_rec = a_rec
exceptions
appl_stack_not_initialized = 1.
re_subrc = sy-subrc.
if re_subrc = 0.
check Receiver is this report
if not ( ( a_rec-rtool = 'RT' and a_rec-ronam = 'RCOPCA02' )
or ( a_rec-rtool = 'TR' and a_rec-ronam = 'KE5Z' ) ) .
re_subrc = 2.
endif.
endif.
endif.
AT SELCTION-SCREEN on value request**********************************
*at selection-screen on value-request for racct-low. "RD "4.6a
"RD "4.6a
call function 'K_RACCT_VALUE_REQUEST' "RD "4.6a
importing "RD "4.6a
e_racct = racct-low. "RD "4.6a
"RD "4.6a
"RD "4.6a
*at selection-screen on value-request for racct-high. "RD "4.6a
"RD "4.6a
call function 'K_RACCT_VALUE_REQUEST' "RD "4.6a
importing "RD "4.6a
e_racct = racct-high. "RD "4.6a
at selection-screen on value-request for p_vari. "MICP40K039857
perform f4_for_variant. "MICP40K039857
at selection-screen on value-request for poper-low. "RD "4.6a
begin of insertion note 522715
call function 'K_KOKRS_READ'
exporting
kokrs = kokrs-low
exceptions
not_found = 1
not_found_gjahr = 2
others = 3.
if sy-subrc = 0.
end of insertion note 522715
call function 'ECPCA_RPMAX_VALUE_REQUEST' "RD "4.6a
exporting "RD "4.6a
i_kokrs = kokrs-low "RD "4.6a
i_ryear = ryear-low "RD "4.6a
importing "RD "4.6a
e_rpmax = poper-low "RD "4.6a
begin of insertion note 522715
exceptions
table_empty = 1.
endif.
end of insertion note 522715
at selection-screen on value-request for poper-high. "RD "4.6a
begin of insertion note 522715
call function 'K_KOKRS_READ'
exporting
kokrs = kokrs-low
exceptions
not_found = 1
not_found_gjahr = 2
others = 3.
if sy-subrc = 0.
end of insertion note 522715
call function 'ECPCA_RPMAX_VALUE_REQUEST' "RD "4.6a
exporting "RD "4.6a
i_kokrs = kokrs-low "RD "4.6a
i_ryear = ryear-low "RD "4.6a
importing "RD "4.6a
e_rpmax = poper-high "RD "4.6a
begin of insertion note 522715
exceptions
table_empty = 1.
endif.
end of insertion note 522715
AT SELCTION-SCREEN ***************************************************
at selection-screen.
perform pai_of_selection_screen.
begin of insertion note 522715
if not kokrs-low is initial.
call function 'K_KOKRS_READ'
exporting
kokrs = kokrs-low
exceptions
not_found = 1
not_found_gjahr = 2
others = 3.
if sy-subrc <> 0.
message e101(ki) with kokrs-low.
endif.
endif.
end of insertion note 522715
archiv
if sy-ucomm = 'FC01' or sy-ucomm = 'UCDS'
or sy-ucomm = 'ONLI' and read_ar = 'X'
and read_as is initial and lr_files[] is initial.
if lt_arch_obj[] is initial.
lt_arch_obj-object = 'PCA_OBJECT'. append lt_arch_obj.
lt_arch_obj-object = 'EC_PCA_ITM'. append lt_arch_obj.
endif.
call function 'KARL_DATA_INPUT_SELECT'
exporting
i_db_and_arc = lc_set
i_infosys_possible = lc_set
i_object_fixed = 'V'
i_documentation = 'KARL_DATA_INPUT_SEL_KE5YZ'
i_report = lc_report
i_reporttype = lc_reporttype
tables
t_objects = lt_arch_obj
t_arch_sel = lr_files
changing
c_xusedb = read_db
c_xusear = read_ar
c_archobj = arc_obj
c_infosys = read_as.
endif.
START-OF-SELECTION **************************************************
start-of-selection.
Default-Werte löschen, falls Aufruf über Recherche
oder Report-Writer erfolgt ist
if no_rrint is initial and ld_no_rrint is initial. "note 490484
if rw_subrc eq 0 or re_subrc eq 0.
refresh: rldnr, rrcty, rvers, kokrs, bukrs, poper, ryear,
racct, prctr, pprctr, drcrk, activ, rhoart, rfarea,
versa, afabe, eprctr,
v_racct, v_prctr, v_pprctr.
clear: rldnr, rrcty, rvers, kokrs, bukrs, poper, ryear,
racct, prctr, pprctr, drcrk, activ, rhoart, rfarea,
versa, afabe, eprctr,
v_racct, v_prctr, v_pprctr.
endif.
Parameter einlesen über Report-Writer-Schnittstelle *
if rw_subrc eq 0.
perform rw_get_parameters.
oder Parameter einlesen über Recherche-Schnittstelle *
elseif re_subrc eq 0.
perform re_get_parameters.
endif.
endif.
if read_db = 'X'. " read from DB (archiv)
Bewegungsdaten einlesen und puffern...................................
call function 'SAPGUI_PROGRESS_INDICATOR'
exporting
text = 'Einzelposten selektieren'(p10).
Use dirty trick to mislead DB-optimizer
call function 'DB_DO_NOT_USE_CLIENT_INDEX'
exporting
value = sy-mandt
tables
mandttab = rclnt.
select (tab_fields) from glpca
client specified
package size packsize
APPENDING CORRESPONDING FIELDS OF TABLE i_glpcaO
into corresponding fields of table i_glpca
where rldnr in rldnr
and rrcty in rrcty
and rvers in rvers
and kokrs in kokrs
and rbukrs in bukrs
and ryear in ryear
and rassc in rassc
and hrkft in hrkft "note 550972
and sbukrs in sbukrs "note 550972
and shoart in shoart "note 550972
and sfarea in sfarea "note 550972
and racct in racct
and rprctr in prctr
and sprctr in pprctr
and poper in poper
and drcrk in drcrk
and activ in activ
and rhoart in rhoart
and rfarea in rfarea
and versa in versa
and eprctr in eprctr
and afabe in afabe
and rmvct in rmvct
and docct in docct
and docnr in docnr
and stagr in stagr
and rtcur in rtcur
and runit in runit
and refdocct in refdocct
and refdocnr in refdocnr
and werks in werks
and rep_matnr in repmatnr "RDIP40K020663
and rscope in rscope "RDIP40K020663
and rclnt in rclnt. "dirty trick to mislead DB-optimizer
if sy-dbcnt > 1.
text1 = sy-dbcnt.
condense text1.
concatenate text1 text-m01 into text2 separated by space.
call function 'SAPGUI_PROGRESS_INDICATOR'
exporting
text = text2. " ... Datensätze gelesen
endif.
endselect.
Entfernt nicht zugehörige Einträge....................................
loop at i_glpca where ( not rprctr in v_prctr )
or ( not sprctr in v_pprctr )
or ( not racct in v_racct ).
delete i_glpca.
endloop.
endif.
*archiv
if read_ar = 'X' and not
( read_as is initial and lr_files[] is initial ).
call function 'SAPGUI_PROGRESS_INDICATOR'
exporting
text = 'Lesen im Archiv'(p12).
define fill_lt_selections.
if not &2[] is initial.
clear ls_selections.
move &1 to ls_selections-fieldname.
loop at &2.
clear ls_selopt.
move-corresponding &2 to ls_selopt.
append ls_selopt to ls_selections-selopt_t.
endloop.
append ls_selections to lt_selections.
endif.
end-of-definition.
fill_lt_selections 'RLDNR' rldnr.
fill_lt_selections 'RRCTY' rrcty.
fill_lt_selections 'RVERS' rvers.
fill_lt_selections 'KOKRS' kokrs.
fill_lt_selections 'RBUKRS' bukrs.
fill_lt_selections 'POPER' poper.
fill_lt_selections 'RYEAR' ryear.
fill_lt_selections 'RPRCTR' prctr.
fill_lt_selections 'SPRCTR' pprctr.
fill_lt_selections 'RACCT' racct.
fill_lt_selections 'DRCRK' drcrk.
fill_lt_selections 'ACTIV' activ.
fill_lt_selections 'RHOART' rhoart.
fill_lt_selections 'RFAREA' rfarea. "note 401961
fill_lt_selections 'STAGR' stagr.
fill_lt_selections 'RTCUR' rtcur.
fill_lt_selections 'RUNIT' runit.
fill_lt_selections 'VERSA' versa.
fill_lt_selections 'EPRCTR' eprctr.
fill_lt_selections 'AFABE' afabe.
fill_lt_selections 'RMVCT' rmvct.
fill_lt_selections 'DOCCT' docct.
fill_lt_selections 'DOCNR' docnr.
fill_lt_selections 'REFDOCCT' refdocct.
fill_lt_selections 'REFDOCNR' refdocnr.
fill_lt_selections 'WERKS' werks.
fill_lt_selections 'REP_MATNR' repmatnr.
fill_lt_selections 'RSCOPE' rscope.
fill_lt_selections 'HRKFT' hrkft. "note 550972
fill_lt_selections 'SBUKRS' sbukrs. "note 550972
fill_lt_selections 'SHOART' shoart. "note 550972
fill_lt_selections 'SFAREA' sfarea. "note 550972
call function 'EC_PCA_SELECT_FROM_ARCHIVE'
exporting
i_selections = lt_selections[]
i_files_sequential_read = lr_files[]
importing
e_glpca = lt_glpca_archiv[]
exceptions
no_infostruc_found = 1.
if sy-subrc = 1.
message id sy-msgid type 'I' number sy-msgno
with sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
endif.
clear i_glpca.
loop at lt_glpca_archiv assigning to i_glpca.
append i_glpca.
endloop.
endif.
if i_glpca[] is initial. "Info,nichts gefunden
message s000.
exit.
endif.
get texts for accounts ...............................................
sort i_glpca by kokrs racct.
loop at i_glpca assigning -racct_ktext = ls_rpcak-ktext.
endloop.
Liste mit Einzelposten geeignet sortieren.............................
call function 'SAPGUI_PROGRESS_INDICATOR'
exporting
text = 'Einzelposten sortieren'(p30).
if show_ref is initial.
sort i_glpca by rldnr ryear rbukrs rrcty rvers
docct docnr docln.
else.
sort i_glpca by rldnr kokrs ryear rbukrs rrcty rvers poper
refdocct refdocnr refdocln.
endif.
Berechtigungsprüfung und gemerkte Belege aufbereiten .................
call function 'SAPGUI_PROGRESS_INDICATOR'
exporting
text = 'Berechtigungsprüfungen'(p40).
clear: cnt_rldnr, cnt_kokrs, cnt_ryear, cnt_rvers, cnt_bukrs.
loop at i_glpca assigning .
Berechtigungscheck
perform check_repo_authority changing authorised.
if authorised is initial.
delete i_glpca.
s_message = 'X'.
zählen der Sätze ohne Berechtigung
auth_dbcount = auth_dbcount + 1.
else. "Weitere Bearbeitung nur für berechtigte Belege...
Zusätzlich merken der Anzahl der Ausprägungen
bestimmter Dimensionen
on change of -rbukrs
ct = '10'
importing
currency = hsl_curr.
endon.
externe Immobilienbezeichnung "ww/kb
on change of i_glpca-imkey.
if ( not -dabrz
I_length = 20
importing
e_empge = -konty.
endif.
CONCATENATE I_GLPCA-KONTY I_GLPCA-EMPGE INTO I_GLPCA-IMBEZ.
endif.
endon.
on change of i_glpca-dabrz.
call function 'REMD_IMKEY_TO_EMPGE'
exporting
i_imkey = i_glpca-imkey
i_dabrz = i_glpca-dabrz
i_length = 20
importing
e_empge = i_glpca-empge
e_konty = i_glpca-konty.
CONCATENATE I_GLPCA-KONTY I_GLPCA-EMPGE INTO I_GLPCA-IMBEZ.
endon.
Konvertierungsproblem mit PSP-Nummer bereinigen
if not -psppp.
endif.
endif.
Währungen in Hilfsfeldern speichern
if -ksl_curr = ksl_curr.
endif.
modify i_glpca.
endif.
endloop.
Nachricht, wenn nicht alle Einzelposten angezeigt werden.
if not s_message is initial.
message s407(km) with auth_dbcount.
endif.
EP ausgeben...........................................................
call function 'SAPGUI_PROGRESS_INDICATOR'
exporting
text = 'Einzelposten ausgeben'(p50).
t_layout-detail_initial_lines = 'X'.
t_layout-detail_popup = 'X'.
t_layout-f2code = 'PIC1'. "MICP40K039857
t_layout-get_selinfos = 'X'.
t_layout-group_change_edit = 'X'. "note 576149
perform fill_listheader.
perform fieldcat_fill.
perform spec_groups_fill.
perform events_fill. "MICP40K039857
">>MICP40K039857
call function 'K_KKB_LIST_DISPLAY'
exporting
i_callback_program = 'RCOPCA02'
i_callback_user_command = 'USR_CMD'
i_callback_top_of_page = 'TOP_OF_PAGE'
I_CALLBACK_END_OF_PAGE =
I_CALLBACK_END_OF_LIST =
i_callback_pf_status_set = 'SET_PF_STATUS'
I_CALLBACK_LAYOUT_SAVE =
I_CALLBACK_FIELDCAT_SAVE =
i_tabname = 'I_GLPCA'
is_layout = t_layout
it_fieldcat = t_fieldcat
I_FCTYPE = 'R'
IT_EXCLUDING =
it_special_groups = t_spec_groups
IT_SORT =
IS_SEL_HIDE =
I_SCREEN_START_COLUMN = 0
I_SCREEN_START_LINE = 0
I_SCREEN_END_COLUMN = 0
I_SCREEN_END_LINE = 0
tables
t_outtab = i_glpca
exceptions
others = 1.
loop at i_glpca.
select single vbeln auart augru
into (l_vbeln, l_auart, l_augru)
from vbak where vbeln = i_glpca-aubel.
if sy-subrc = 0.
move l_auart to i_glpca-v_auart.
move l_augru to i_glpca-v_augru.
modify i_glpca.
endif.
endloop.
call function 'REUSE_ALV_GRID_DISPLAY'
CALL FUNCTION 'REUSE_ALV_LIST_DISPLAY'
exporting
I_INTERFACE_CHECK = ' '
i_callback_program = 'ZRCOPCA02'
i_callback_pf_status_set = 'SET_PF_STATUS'
i_callback_user_command = 'USR_CMD'
i_structure_name = 'I_GLPCA'
is_layout = t_layout
it_fieldcat = t_fieldcat
IT_EXCLUDING =
it_special_groups = t_spec_groups
IT_SORT =
IT_FILTER =
IS_SEL_HIDE =
i_default = 'X'
i_save = g_save
is_variant = g_variant
it_events = t_events
IT_EVENT_EXIT =
IS_PRINT =
I_SCREEN_START_COLUMN = 0
I_SCREEN_START_LINE = 0
I_SCREEN_END_COLUMN = 0
I_SCREEN_END_LINE = 0
IMPORTING
E_EXIT_CAUSED_BY_CALLER =
ES_EXIT_CAUSED_BY_USER =
tables
t_outtab = i_glpca
exceptions
program_error = 1
others = 2.
if sy-subrc <> 0.
message id sy-msgid type sy-msgty number sy-msgno
with sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
endif.
"<<MICP40K039857
clear i_glpca.
*& Form CHECK_REPO_AUTHORITY
Check only new auth-object K_PCA *
--> p1 text
<-- p2 text
form check_repo_authority changing authorized like authorised.
fill structure for userexit in K_PCA_RESP_AUTHORITY_CHECK
data: auth like pca_i_auth. "46a MIC check K_PCA and G_GLTP
auth-bukrs = -rrcty.
clear authorized.
check PrCtr/account/activity
call function 'K_PCA_RESP_AUTHORITY_CHECK'
exporting
i_kokrs = -racct
i_vorgn = 'REPP'
i_actvt = '28'
i_auth = auth
i_no_dialog_message = 'X'
exceptions
no_authority = 1
data_missing = 2
others = 3.
if sy-subrc = 0. "ok
check ledger/version/record type
call function 'PCA_G_GLTP_AUTH_CHECK'
exporting
rldnr = -rrcty
exceptions
no_authorisation = 1
others = 2.
if sy-subrc = 0. "ok, User is authorized
authorized = 'X'.
endif.
endif.
endform. " CHECK_REPO_AUTHORITY
*& Form INIT_VARS
Initialisieren diverser Hilfsvariablen und -tabellen *
form init_vars.
data begin of nametab occurs 80. "Tabelle mit Feldern aus der RPCA2
include structure dntab.
data end of nametab.
select single * from t000
client specified
where mandt = sy-mandt.
refresh nametab.
call function 'NAMETAB_GET'
exporting
only = 'T'
tabname = 'RPCA2'
tables
nametab = nametab.
Übernehmen der Feldnamen, die auch in der GLPCA
vorkommen.
loop at nametab where fieldname ne 'KSL_CURR'
and fieldname ne 'HSL_CURR'
and fieldname ne 'EMPGE' "ww/kb
and fieldname ne 'KONTY'. "ww/kb
move nametab-fieldname to tab_fields-name.
append tab_fields.
endloop.
fill Fields of receiver for BBS "MIC46C
call function 'RSTI_REPORT_FIELDS_FIND'
exporting
e_repid = 'RCOPCA02'
e_type = 'R'
tables
it_fields = bbs_fieldtab.
correct fieldnames
read table bbs_fieldtab with key rfield = 'PRCTR'.
if sy-subrc = 0.
bbs_fieldtab-rfield = 'RPRCTR'.
modify bbs_fieldtab index sy-tabix.
endif.
read table bbs_fieldtab with key rfield = 'PPRCTR'.
if sy-subrc = 0.
bbs_fieldtab-rfield = 'SPRCTR'.
modify bbs_fieldtab index sy-tabix.
endif.
read table bbs_fieldtab with key rfield = 'BUKRS'.
if sy-subrc = 0.
bbs_fieldtab-rfield = 'RBUKRS'.
modify bbs_fieldtab index sy-tabix.
endif.
Unicode
class cl_abap_char_utilities definition load.
clear hex00 with cl_abap_char_utilities=>minchar.
clear hexff with cl_abap_char_utilities=>maxchar.
endform. " INIT_VARS
FORM FILL_LISTHEADER *
List-Header in Abhängigkeit der selektierten Daten *
form fill_listheader.
read table i_glpca index 1.
if sy-subrc ne 0.
exit.
endif.
t_listheader-typ = 'S'.
t_listheader-key = 'Ledger '(h01).
if cnt_rldnr <= 1.
t_listheader-info = i_glpca-rldnr.
else.
t_listheader-info = '*'.
endif.
append t_listheader.
t_listheader-typ = 'S'.
t_listheader-key = 'Kostenrechnungskreis'(h02).
if cnt_kokrs <= 1.
t_listheader-info = i_glpca-kokrs.
else.
t_listheader-info = '*'.
endif.
append t_listheader.
t_listheader-typ = 'S'.
t_listheader-key = 'Buchungskreis '(h03).
if cnt_bukrs <= 1.
t_listheader-info = i_glpca-rbukrs.
else.
t_listheader-info = '*'.
endif.
append t_listheader.
t_listheader-typ = 'S'.
t_listheader-key = 'Buchungsperiode '(h04).
if cnt_poper <= 1.
t_listheader-info = i_glpca-poper.
else.
t_listheader-info = '*'.
endif.
append t_listheader.
if cnt_ryear <= 1.
t_listheader-typ = 'S'.
t_listheader-key = 'Geschäftsjahr '(h05).
t_listheader-info = i_glpca-ryear.
append t_listheader.
endif.
t_listheader-typ = 'S'.
t_listheader-key = 'Version '(h06).
if cnt_rvers <= 1.
t_listheader-info = i_glpca-rvers.
else.
t_listheader-info = '*'.
endif.
append t_listheader.
endform. "fill_listheader
*& Form FIELDCAT_FILL
*& Aufbau des Feldkataloges für den K_KKB_LIST_DISPLAY, *
*& bzw REUSE_ALV_LIST_DISPLAY, *
*& weitere Infos enthält die FktBaustein-Doku *
form fieldcat_fill.
data: i type i value 0.
refresh t_fieldcat.
Ledger
if cnt_rldnr > 1.
add 1 to i.
clear afield.
afield-col_pos = i.
afield-fieldname = 'RLDNR'.
afield-no_sum = 'X'.
afield-no_out = 'X'.
afield-key = 'X'.
afield-ref_tabname = 'GLPCA'.
afield-sp_group = '1'.
append afield to t_fieldcat.
endif.
Satzart
add 1 to i.
clear afield.
afield-col_pos = i.
afield-fieldname = 'RRCTY'.
afield-no_sum = 'X'.
afield-ref_tabname = 'GLPCA'.
afield-no_out = 'X'.
afield-sp_group = '1'.
append afield to t_fieldcat.
Version
if cnt_rvers > 1.
add 1 to i.
clear afield.
afield-col_pos = i.
afield-fieldname = 'RVERS'.
afield-no_sum = 'X'.
afield-ref_tabname = 'GLPCA'.
afield-no_out = 'X'.
afield-sp_group = '1'.
append afield to t_fieldcat.
endif.
Periode
if cnt_poper > 1.
add 1 to i.
clear afield.
afield-col_pos = i.
afield-fieldname = 'POPER'.
afield-no_sum = 'X'.
afield-ref_tabname = 'GLPCA'.
afield-no_out = 'X'.
afield-sp_group = '1'.
append afield to t_fieldcat.
endif.
Geschäftsjahr
if cnt_ryear > 1.
add 1 to i.
clear afield.
afield-col_pos = i.
afield-fieldname = 'RYEAR'.
afield-no_sum = 'X'.
afield-ref_tabname = 'GLPCA'.
afield-no_out = 'X'.
afield-sp_group = '1'.
append afield to t_fieldcat.
endif.
Referenzbelegtyp
add 1 to i.
clear afield.
afield-col_pos = i.
afield-fieldname = 'REFDOCCT'.
afield-ref_tabname = 'GLPCA'.
afield-key_sel = 'X'.
afield-no_sum = 'X'.
afield-sp_group = '2'.
afield-seltext_s = 'Typ'(t01).
afield-seltext_m = 'Belegtyp'(t02).
afield-seltext_l = 'Ref.Belegtyp'(t03).
afield-outputlen = 3. "Platz für die Sterne der Zwischensummen
if not show_ref is initial.
afield-key = 'X'.
else.
afield-no_out = 'X'.
endif.
append afield to t_fieldcat.
Referenzbelegnummer
add 1 to i.
clear afield.
afield-col_pos = i.
afield-fieldname = 'REFDOCNR'.
afield-ref_tabname = 'GLPCA'.
afield-key_sel = 'X'.
afield-no_sum = 'X'.
afield-sp_group = '2'.
afield-seltext_s = 'Refbeleg'(t04).
afield-seltext_m = 'Refbelegnr'(t05).
afield-seltext_l = 'Ref.Belegnummer'(t06).
if not show_ref is initial.
afield-key = 'X'.
else.
afield-no_out = 'X'.
endif.
appendHi Prabhu,
You are right, problem is with Field Catalog...
When I use FM 'REUSE_ALV_GRID_DISPLAY' it is dumping...
When i tried with FM 'REUSE_ALV_LIST_DISPLAY' it is working perfectly....
how can i use FM 'REUSE_ALV_GRID_DISPLAY' without dumping????
do i need to pass any thing in FM????
Here is the dump:
Runtime Errors MESSAGE_TYPE_X
Occurred on 12/21/2006 at 01:03:24
The current application triggered a termination with a short dump.
What happened?
The current application program detected a situation which really
should not occur. Therefore, a termination with a short dump was
triggered on purpose by the key word MESSAGE (type X).
Error analysis
Short text of error message:
Technical information about the message:
Message classe...... "0K "
Number.............. 000
User, transaction...
Language key........ "E"
Transaction......... "SE38 "
Program............. "SAPLSLVC "
Screen.............. "SAPLSLVC_FULLSCREEN 0500"
Screen line......... 3
Information on where termination occurred
The termination occurred in the ABAP program "SAPLSLVC " in "LINE_OUT_NEW_2".
The main program was "ZRCOPCA02 ".
The termination occurred in line 918 of the source code of the (Include)
program "LSLVCF01 "
of the source code of program "LSLVCF01 " (when calling the editor 9180).
Source code extract
008880 gs_roid-row_id = rs_row-index * -1.
008890 endif.
008900 gs_roid-sub_row_id = rs_row-rowtype+7(10).
008910 gs_poid-row_id = gs_roid-row_id.
008920 gs_poid-sub_row_id = gs_roid-sub_row_id.
008930 gs_poid-rowtype = rs_row-rowtype.
008940 gs_poid-index = rs_row-index.
008950 insert gs_poid into table rt_poid.
008960 endif.
008970 append gs_roid to rt_roid.
008980
008990 loop at rt_fieldcat assigning <ls_fieldcat> where tech ne 'X' and
009000 no_out ne 'X'.
009010
009020 if gflg_invisible = 'X'.
009030 if <ls_fieldcat>-do_sum is initial.
009040 clear gflg_invisible.
009050 continue.
009060 else.
009070 clear g_col_counter.
009080 clear gflg_invisible.
009090 endif.
009100 endif.
009110
009120 clear gs_lvc_data.
009130 clear g_style.
009140
009150 assign component
009160 <ls_fieldcat>-fieldname of structure rt_data to <g_field>.
009170 if sy-subrc ne 0.
> message x000(0k).
009190 endif.
009200
009210 g_col_counter = g_col_counter + 1.
009220
009230 gs_lvc_data-row_pos = r_row_counter.
009240 gs_lvc_data-col_pos = g_col_counter.
009250 gs_lvc_data-row_id = gs_roid-row_id.
009260 gs_lvc_data-sub_row_id = gs_roid-sub_row_id.
009270
009280 * Endtotal and average
009290 if rs_row-rowtype(1) ca 'T' and <ls_fieldcat>-do_sum = 'C'.
009300 * save the actual grouplevel information
009310 gs_grouplevels = rs_grouplevels.
009320 clear g_lines.
009330
009340 * get number of lines of the collect table
009350 describe table rt_data lines g_lines.
009360 * if there is only one line or the field has no references so
009370 * that only the first line has to be considered
Thanks,
fractal
null -
Useful Interview Questions and Answere
Hi All
Some of the Real time question.
Q) Under which menu path is the Test Workbench to be found, including in earlier Releases?
The menu path is: Tools - ABAP Workbench - Test - Test Workbench.
Q) I want to delete a BEx query that is in Production system through request. Is anyone aware about it?
A) Have you tried the RSZDELETE transaction?
Q) Errors while monitoring process chains.
A) During data loading. Apart from them, in process chains you add so many process types, for example after loading data into Info Cube, you rollup data into aggregates, now this rolling up of data into aggregates is a process type which you keep after the process type for loading data into Cube. This rolling up into aggregates might fail.
Another one is after you load data into ODS, you activate ODS data (another process type) this might also fail.
Q) In Monitor----- Details (Header/Status/Details) à Under Processing (data packet): Everything OK à Context menu of Data Package 1 (1 Records): Everything OK -
Simulate update. (Here we can debug update rules or transfer rules.)
SM50 à Program/Mode à Program à Debugging & debug this work process.
Q) PSA Cleansing.
A) You know how to edit PSA. I don't think you can delete single records. You have to delete entire PSA data for a request.
Q) Can we make a datasource to support delta.
A) If this is a custom (user-defined) datasource you can make the datasource delta enabled. While creating datasource from RSO2, after entering datasource name and pressing create, in the next screen there is one button at the top, which says generic delta. If you want more details about this there is a chapter in Extraction book, it's in last pages u find out.
Generic delta services: -
Supports delta extraction for generic extractors according to:
Time stamp
Calendar day
Numeric pointer, such as document number & counter
Only one of these attributes can be set as a delta attribute.
Delta extraction is supported for all generic extractors, such as tables/views, SAP Query and function modules
The delta queue (RSA7) allows you to monitor the current status of the delta attribute
Q) Workbooks, as a general rule, should be transported with the role.
Here are a couple of scenarios:
1. If both the workbook and its role have been previously transported, then the role does not need to be part of the transport.
2. If the role exists in both dev and the target system but the workbook has never been transported, and then you have a choice of transporting the role (recommended) or just the workbook. If only the workbook is transported, then an additional step will have to be taken after import: Locate the WorkbookID via Table RSRWBINDEXT (in Dev and verify the same exists in the target system) and proceed to manually add it to the role in the target system via Transaction Code PFCG -- ALWAYS use control c/control v copy/paste for manually adding!
3. If the role does not exist in the target system you should transport both the role and workbook. Keep in mind that a workbook is an object unto itself and has no dependencies on other objects. Thus, you do not receive an error message from the transport of 'just a workbook' -- even though it may not be visible, it will exist (verified via Table RSRWBINDEXT).
Overall, as a general rule, you should transport roles with workbooks.
Q) How much time does it take to extract 1 million (10 lackhs) of records into an infocube?
A. This depends, if you have complex coding in update rules it will take longer time, or else it will take less than 30 minutes.
Q) What are the five ASAP Methodologies?
A: Project plan, Business Blue print, Realization, Final preparation & Go-Live - support.
1. Project Preparation: In this phase, decision makers define clear project objectives and an efficient decision making process (i.e. Discussions with the client, like what are his needs and requirements etc.). Project managers will be involved in this phase (I guess).
A Project Charter is issued and an implementation strategy is outlined in this phase.
2. Business Blueprint: It is a detailed documentation of your company's requirements. (i.e. what are the objects we need to develop are modified depending on the client's requirements).
3. Realization: In this only, the implementation of the project takes place (development of objects etc) and we are involved in the project from here only.
4. Final Preparation: Final preparation before going live i.e. testing, conducting pre-go-live, end user training etc.
End user training is given that is in the client site you train them how to work with the new environment, as they are new to the technology.
5. Go-Live & support: The project has gone live and it is into production. The Project team will be supporting the end users.
Q) What is landscape of R/3 & what is landscape of BW. Landscape of R/3 not sure.
Then Landscape of b/w: u have the development system, testing system, production system
Development system: All the implementation part is done in this sys. (I.e., Analysis of objects developing, modification etc) and from here the objects are transported to the testing system, but before transporting an initial test known as Unit testing (testing of objects) is done in the development sys.
Testing/Quality system: quality check is done in this system and integration testing is done.
Production system: All the extraction part takes place in this sys.
Q) How do you measure the size of infocube?
A: In no of records.
Q). Difference between infocube and ODS?
A: Infocube is structured as star schema (extended) where a fact table is surrounded by different dim table that are linked with DIM'ids. And the data wise, you will have aggregated data in the cubes. No overwrite functionality
ODS is a flat structure (flat table) with no star schema concept and which will have granular data (detailed level). Overwrite functionality.
Flat file datasources does not support 0recordmode in extraction.
x before, -after, n new, a add, d delete, r reverse
Q) Difference between display attributes and navigational attributes?
A: Display attribute is one, which is used only for display purpose in the report. Where as navigational attribute is used for drilling down in the report. We don't need to maintain Navigational attribute in the cube as a characteristic (that is the advantage) to drill down.
Q. SOME DATA IS UPLOADED TWICE INTO INFOCUBE. HOW TO CORRECT IT?
A: But how is it possible? If you load it manually twice, then you can delete it by requestID.
Q. CAN U ADD A NEW FIELD AT THE ODS LEVEL?
Sure you can. ODS is nothing but a table.
Q. CAN NUMBER OF DATASOURCES HAVE ONE INFOSOURCE?
A) Yes of course. For example, for loading text and hierarchies we use different data sources but the same InfoSource.
Q. BRIEF THE DATAFLOW IN BW.
A) Data flows from transactional system to analytical system (BW). DataSources on the transactional system needs to be replicated on BW side and attached to infosource and update rules respectively.
Q. CURRENCY CONVERSIONS CAN BE WRITTEN IN UPDATE RULES. WHY NOT IN TRANSFER RULES?
Q) WHAT IS PROCEDURE TO UPDATE DATA INTO DATA TARGETS?
FULL and DELTA.
Q) AS WE USE Sbwnn, sbiw1, sbiw2 for delta update in LIS THEN WHAT IS THE PROCEDURE IN LO-COCKPIT?
No LIS in LO cockpit. We will have datasources and can be maintained (append fields). Refer white paper on LO-Cockpit extractions.
Q) Why we delete the setup tables (LBWG) & fill them (OLI*BW)?
A) Initially we don't delete the setup tables but when we do change in extract structure we go for it. We r changing the extract structure right, that means there are some newly added fields in that which r not before. So to get the required data (i.e.; the data which is required is taken and to avoid redundancy) we delete n then fill the setup tables.
To refresh the statistical data. The extraction set up reads the dataset that you want to process such as, customers orders with the tables like VBAK, VBAP) & fills the relevant communication structure with the data. The data is stored in cluster tables from where it is read when the initialization is run. It is important that during initialization phase, no one generates or modifies application data, at least until the tables can be set up.
Q) SIGNIFICANCE of ODS?
It holds granular data (detailed level).
Q) WHERE THE PSA DATA IS STORED?
In PSA table.
Q) WHAT IS DATA SIZE?
The volume of data one data target holds (in no. of records)
Q) Different types of INFOCUBES.
Basic, Virtual (remote, sap remote and multi)
Virtual Cube is used for example, if you consider railways reservation all the information has to be updated online. For designing the Virtual cube you have to write the function module that is linking to table, Virtual cube it is like a the structure, when ever the table is updated the virtual cube will fetch the data from table and display report Online... FYI.. you will get the information : https://www.sdn.sap.com/sdn/index.sdn and search for Designing Virtual Cube and you will get a good material designing the Function Module
Q) INFOSET QUERY.
Can be made of ODS's and Characteristic InfoObjects with masterdata.
Q) IF THERE ARE 2 DATASOURCES HOW MANY TRANSFER STRUCTURES ARE THERE.
In R/3 or in BW? 2 in R/3 and 2 in BW
Q) ROUTINES?
Exist in the InfoObject, transfer routines, update routines and start routine
Q) BRIEF SOME STRUCTURES USED IN BEX.
Rows and Columns, you can create structures.
Q) WHAT ARE THE DIFFERENT VARIABLES USED IN BEX?
Different Variable's are Texts, Formulas, Hierarchies, Hierarchy nodes & Characteristic values.
Variable Types are
Manual entry /default value
Replacement path
SAP exit
Customer exit
Authorization
Q) HOW MANY LEVELS YOU CAN GO IN REPORTING?
You can drill down to any level by using Navigational attributes and jump targets.
Q) WHAT ARE INDEXES?
Indexes are data base indexes, which help in retrieving data fastly.
Q) DIFFERENCE BETWEEN 2.1 AND 3.X VERSIONS.
Help! Refer documentation
Q) IS IT NESSESARY TO INITIALIZE EACH TIME THE DELTA UPDATE IS USED?
No.
Q) WHAT IS THE SIGNIFICANCE OF KPI'S?
KPI's indicate the performance of a company. These are key figures
Q) AFTER THE DATA EXTRACTION WHAT IS THE IMAGE POSITION.
After image (correct me if I am wrong)
Q) REPORTING AND RESTRICTIONS.
Help! Refer documentation.
Q) TOOLS USED FOR PERFORMANCE TUNING.
ST22, Number ranges, delete indexes before load. Etc
Q) PROCESS CHAINS: IF U has USED IT THEN HOW WILL U SCHEDULING DATA DAILY.
There should be some tool to run the job daily (SM37 jobs)
Q) AUTHORIZATIONS.
Profile generator
Q) WEB REPORTING.
What are you expecting??
Q) CAN CHARECTERSTIC INFOOBJECT CAN BE INFOPROVIDER.
Of course
Q) PROCEDURES OF REPORTING ON MULTICUBES
Refer help. What are you expecting? MultiCube works on Union condition
Q) EXPLAIN TRANPSORTATION OF OBJECTS?
Dev-àQ and Dev-----àP
Q) What types of partitioning are there for BW?
There are two Partitioning Performance aspects for BW (Cube & PSA)
Query Data Retrieval Performance Improvement:
Partitioning by (say) Date Range improves data retrieval by making best use of database execution plans and indexes (of say Oracle database engine).
B) Transactional Load Partitioning Improvement:
Partitioning based on expected load volumes and data element sizes. Improves data loading into PSA and Cubes by infopackages (Eg. without timeouts).
Q) How can I compare data in R/3 with data in a BW Cube after the daily delta loads? Are there any standard procedures for checking them or matching the number of records?
A) You can go to R/3 TCode RSA3 and run the extractor. It will give you the number of records extracted. Then go to BW Monitor to check the number of records in the PSA and check to see if it is the same & also in the monitor header tab.
A) RSA3 is a simple extractor checker program that allows you to rule out extracts problems in R/3. It is simple to use, but only really tells you if the extractor works. Since records that get updated into Cubes/ODS structures are controlled by Update Rules, you will not be able to determine what is in the Cube compared to what is in the R/3 environment. You will need to compare records on a 1:1 basis against records in R/3 transactions for the functional area in question. I would recommend enlisting the help of the end user community to assist since they presumably know the data.
To use RSA3, go to it and enter the extractor ex: 2LIS_02_HDR. Click execute and you will see the record count, you can also go to display that data. You are not modifying anything so what you do in RSA3 has no effect on data quality afterwards. However, it will not tell you how many records should be expected in BW for a given load. You have that information in the monitor RSMO during and after data loads. From RSMO for a given load you can determine how many records were passed through the transfer rules from R/3, how many targets were updated, and how many records passed through the Update Rules. It also gives you error messages from the PSA.
Q) Types of Transfer Rules?
A) Field to Field mapping, Constant, Variable & routine.
Q) Types of Update Rules?
A) (Check box), Return table
Q) Transfer Routine?
A) Routines, which we write in, transfer rules.
Q) Update Routine?
A) Routines, which we write in Update rules
Q) What is the difference between writing a routine in transfer rules and writing a routine in update rules?
A) If you are using the same InfoSource to update data in more than one data target its better u write in transfer rules because u can assign one InfoSource to more than one data target & and what ever logic u write in update rules it is specific to particular one data target.
Q) Routine with Return Table.
A) Update rules generally only have one return value. However, you can create a routine in the tab strip key figure calculation, by choosing checkbox Return table. The corresponding key figure routine then no longer has a return value, but a return table. You can then generate as many key figure values, as you like from one data record.
Q) Start routines?
A) Start routines u can write in both updates rules and transfer rules, suppose you want to restrict (delete) some records based on conditions before getting loaded into data targets, then you can specify this in update rules-start routine.
Ex: - Delete Data_Package ani ante it will delete a record based on the condition
Q) X & Y Tables?
X-table = A table to link material SIDs with SIDs for time-independent navigation attributes.
Y-table = A table to link material SIDs with SIDS for time-dependent navigation attributes.
There are four types of sid tables
X time independent navigational attributes sid tables
Y time dependent navigational attributes sid tables
H hierarchy sid tables
I hierarchy structure sid tables
Q) Filters & Restricted Key figures (real time example)
Restricted KF's u can have for an SD cube: billed quantity, billing value, no: of billing documents as RKF's.
Q) Line-Item Dimension (give me an real time example)
Line-Item Dimension: Invoice no: or Doc no: is a real time example
Q) What does the number in the 'Total' column in Transaction RSA7 mean?
A) The 'Total' column displays the number of LUWs that were written in the delta queue and that have not yet been confirmed. The number includes the LUWs of the last delta request (for repetition of a delta request) and the LUWs for the next delta request. A LUW only disappears from the RSA7 display when it has been transferred to the BW System and a new delta request has been received from the BW System.
Q) How to know in which table (SAP BW) contains Technical Name / Description and creation data of a particular Reports. Reports that are created using BEx Analyzer.
A) There is no such table in BW if you want to know such details while you are opening a particular query press properties button you will come to know all the details that you wanted.
You will find your information about technical names and description about queries in the following tables. Directory of all reports (Table RSRREPDIR) and Directory of the reporting component elements (Table RSZELTDIR) for workbooks and the connections to queries check Where- used list for reports in workbooks (Table RSRWORKBOOK) Titles of Excel Workbooks in InfoCatalog (Table RSRWBINDEXT)
Q) What is a LUW in the delta queue?
A) A LUW from the point of view of the delta queue can be an individual document, a group of documents from a collective run or a whole data packet of an application extractor.
Q) Why does the number in the 'Total' column in the overview screen of Transaction RSA7 differ from the number of data records that is displayed when you call the detail view?
A) The number on the overview screen corresponds to the total of LUWs (see also first question) that were written to the qRFC queue and that have not yet been confirmed. The detail screen displays the records contained in the LUWs. Both, the records belonging to the previous delta request and the records that do not meet the selection conditions of the preceding delta init requests are filtered out. Thus, only the records that are ready for the next delta request are displayed on the detail screen. In the detail screen of Transaction RSA7, a possibly existing customer exit is not taken into account.
Q) Why does Transaction RSA7 still display LUWs on the overview screen after successful delta loading?
A) Only when a new delta has been requested does the source system learn that the previous delta was successfully loaded to the BW System. Then, the LUWs of the previous delta may be confirmed (and also deleted). In the meantime, the LUWs must be kept for a possible delta request repetition. In particular, the number on the overview screen does not change when the first delta was loaded to the BW System.
Q) Why are selections not taken into account when the delta queue is filled?
A) Filtering according to selections takes place when the system reads from the delta queue. This is necessary for reasons of performance.
Q) Why is there a DataSource with '0' records in RSA7 if delta exists and has also been loaded successfully?
It is most likely that this is a DataSource that does not send delta data to the BW System via the delta queue but directly via the extractor (delta for master data using ALE change pointers). Such a DataSource should not be displayed in RSA7. This error is corrected with BW 2.0B Support Package 11.
Q) Do the entries in table ROIDOCPRMS have an impact on the performance of the loading procedure from the delta queue?
A) The impact is limited. If performance problems are related to the loading process from the delta queue, then refer to the application-specific notes (for example in the CO-PA area, in the logistics cockpit area and so on).
Caution: As of Plug In 2000.2 patch 3 the entries in table ROIDOCPRMS are as effective for the delta queue as for a full update. Please note, however, that LUWs are not split during data loading for consistency reasons. This means that when very large LUWs are written to the DeltaQueue, the actual package size may differ considerably from the MAXSIZE and MAXLINES parameters.
Q) Why does it take so long to display the data in the delta queue (for example approximately 2 hours)?
A) With Plug In 2001.1 the display was changed: the user has the option of defining the amount of data to be displayed, to restrict it, to selectively choose the number of a data record, to make a distinction between the 'actual' delta data and the data intended for repetition and so on.
Q) What is the purpose of function 'Delete data and meta data in a queue' in RSA7? What exactly is deleted?
A) You should act with extreme caution when you use the deletion function in the delta queue. It is comparable to deleting an InitDelta in the BW System and should preferably be executed there. You do not only delete all data of this DataSource for the affected BW System, but also lose the entire information concerning the delta initialization. Then you can only request new deltas after another delta initialization.
When you delete the data, the LUWs kept in the qRFC queue for the corresponding target system are confirmed. Physical deletion only takes place in the qRFC outbound queue if there are no more references to the LUWs.
The deletion function is for example intended for a case where the BW System, from which the delta initialization was originally executed, no longer exists or can no longer be accessed.
Q) Why does it take so long to delete from the delta queue (for example half a day)?
A) Import PlugIn 2000.2 patch 3. With this patch the performance during deletion is considerably improved.
Q) Why is the delta queue not updated when you start the V3 update in the logistics cockpit area?
A) It is most likely that a delta initialization had not yet run or that the delta initialization was not successful. A successful delta initialization (the corresponding request must have QM status 'green' in the BW System) is a prerequisite for the application data being written in the delta queue.
Q) What is the relationship between RSA7 and the qRFC monitor (Transaction SMQ1)?
A) The qRFC monitor basically displays the same data as RSA7. The internal queue name must be used for selection on the initial screen of the qRFC monitor. This is made up of the prefix 'BW, the client and the short name of the DataSource. For DataSources whose name are 19 characters long or shorter, the short name corresponds to the name of the DataSource. For DataSources whose name is longer than 19 characters (for delta-capable DataSources only possible as of PlugIn 2001.1) the short name is assigned in table ROOSSHORTN.
In the qRFC monitor you cannot distinguish between repeatable and new LUWs. Moreover, the data of a LUW is displayed in an unstructured manner there.
Q) Why are the data in the delta queue although the V3 update was not started?
A) Data was posted in background. Then, the records are updated directly in the delta queue (RSA7). This happens in particular during automatic goods receipt posting (MRRS). There is no duplicate transfer of records to the BW system. See Note 417189.
Q) Why does button 'Repeatable' on the RSA7 data details screen not only show data loaded into BW during the last delta but also data that were newly added, i.e. 'pure' delta records?
A) Was programmed in a way that the request in repeat mode fetches both actually repeatable (old) data and new data from the source system.
Q) I loaded several delta inits with various selections. For which one is the delta loaded?
A) For delta, all selections made via delta inits are summed up. This means, a delta for the 'total' of all delta initializations is loaded.
Q) How many selections for delta inits are possible in the system?
A) With simple selections (intervals without complicated join conditions or single values), you can make up to about 100 delta inits. It should not be more.
With complicated selection conditions, it should be only up to 10-20 delta inits.
Reason: With many selection conditions that are joined in a complicated way, too many 'where' lines are generated in the generated ABAP source code that may exceed the memory limit.
Q) I intend to copy the source system, i.e. make a client copy. What will happen with may delta? Should I initialize again after that?
A) Before you copy a source client or source system, make sure that your deltas have been fetched from the DeltaQueue into BW and that no delta is pending. After the client copy, an inconsistency might occur between BW delta tables and the OLTP delta tables as described in Note 405943. After the client copy, Table ROOSPRMSC will probably be empty in the OLTP since this table is client-independent. After the system copy, the table will contain the entries with the old logical system name that are no longer useful for further delta loading from the new logical system. The delta must be initialized in any case since delta depends on both the BW system and the source system. Even if no dump 'MESSAGE_TYPE_X' occurs in BW when editing or creating an InfoPackage, you should expect that the delta have to be initialized after the copy.
Q) Is it allowed in Transaction SMQ1 to use the functions for manual control of processes?
A) Use SMQ1 as an instrument for diagnosis and control only. Make changes to BW queues only after informing the BW Support or only if this is explicitly requested in a note for component 'BC-BW' or 'BW-WHM-SAPI'.
Q) Despite of the delta request being started after completion of the collective run (V3 update), it does not contain all documents. Only another delta request loads the missing documents into BW. What is the cause for this "splitting"?
A) The collective run submits the open V2 documents for processing to the task handler, which processes them in one or several parallel update processes in an asynchronous way. For this reason, plan a sufficiently large "safety time window" between the end of the collective run in the source system and the start of the delta request in BW. An alternative solution where this problem does not occur is described in Note 505700.
Q) Despite my deleting the delta init, LUWs are still written into the DeltaQueue?
A) In general, delta initializations and deletions of delta inits should always be carried out at a time when no posting takes place. Otherwise, buffer problems may occur: If a user started the internal mode at a time when the delta initialization was still active, he/she posts data into the queue even though the initialization had been deleted in the meantime. This is the case in your system.
Q) In SMQ1 (qRFC Monitor) I have status 'NOSEND'. In the table TRFCQOUT, some entries have the status 'READY', others 'RECORDED'. ARFCSSTATE is 'READ'. What do these statuses mean? Which values in the field 'Status' mean what and which values are correct and which are alarming? Are the statuses BW-specific or generally valid in qRFC?
A) Table TRFCQOUT and ARFCSSTATE: Status READ means that the record was read once either in a delta request or in a repetition of the delta request. However, this does not mean that the record has successfully reached the BW yet. The status READY in the TRFCQOUT and RECORDED in the ARFCSSTATE means that the record has been written into the DeltaQueue and will be loaded into the BW with the next delta request or a repetition of a delta. In any case only the statuses READ, READY and RECORDED in both tables are considered to be valid. The status EXECUTED in TRFCQOUT can occur temporarily. It is set before starting a DeltaExtraction for all records with status READ present at that time. The records with status EXECUTED are usually deleted from the queue in packages within a delta request directly after setting the status before extracting a new delta. If you see such records, it means that either a process which is confirming and deleting records which have been loaded into the BW is successfully running at the moment, or, if the records remain in the table for a longer period of time with status EXECUTED, it is likely that there are problems with deleting the records which have already been successfully been loaded into the BW. In this state, no more deltas are loaded into the BW. Every other status is an indicator for an error or an inconsistency. NOSEND in SMQ1 means nothing (see note 378903).
The value 'U' in field 'NOSEND' of table TRFCQOUT is discomforting.
Q) The extract structure was changed when the DeltaQueue was empty. Afterwards new delta records were written to the DeltaQueue. When loading the delta into the PSA, it shows that some fields were moved. The same result occurs when the contents of the DeltaQueue are listed via the detail display. Why are the data displayed differently? What can be done?
Make sure that the change of the extract structure is also reflected in the database and that all servers are synchronized. We recommend to reset the buffers using Transaction $SYNC. If the extract structure change is not communicated synchronously to the server where delta records are being created, the records are written with the old structure until the new structure has been generated. This may have disastrous consequences for the delta.
When the problem occurs, the delta needs to be re-initialized.
Q) How and where can I control whether a repeat delta is requested?
A) Via the status of the last delta in the BW Request Monitor. If the request is RED, the next load will be of type 'Repeat'. If you need to repeat the last load for certain reasons, set the request in the monitor to red manually. For the contents of the repeat see Question 14. Delta requests set to red despite of data being already updated lead to duplicate records in a subsequent repeat, if they have not been deleted from the data targets concerned before.
Q) As of PI 2003.1, the Logistic Cockpit offers various types of update methods. Which update method is recommended in logistics? According to which criteria should the decision be made? How can I choose an update method in logistics?
See the recommendation in Note 505700.
Q) Are there particular recommendations regarding the data volume the DeltaQueue may grow to without facing the danger of a read failure due to memory problems?
A) There is no strict limit (except for the restricted number range of the 24-digit QCOUNT counter in the LUW management table - which is of no practical importance, however - or the restrictions regarding the volume and number of records in a database table).
When estimating "smooth" limits, both the number of LUWs is important and the average data volume per LUW. As a rule, we recommend to bundle data (usually documents) already when writing to the DeltaQueue to keep number of LUWs small (partly this can be set in the applications, e.g. in the Logistics Cockpit). The data volume of a single LUW should not be considerably larger than 10% of the memory available to the work process for data extraction (in a 32-bit architecture with a memory volume of about 1GByte per work process, 100 Mbytes per LUW should not be exceeded). That limit is of rather small practical importance as well since a comparable limit already applies when writing to the DeltaQueue. If the limit is observed, correct reading is guaranteed in most cases.
If the number of LUWs cannot be reduced by bundling application transactions, you should at least make sure that the data are fetched from all connected BWs as quickly as possible. But for other, BW-specific, reasons, the frequency should not be higher than one DeltaRequest per hour.
To avoid memory problems, a program-internal limit ensures that never more than 1 million LUWs are read and fetched from the database per DeltaRequest. If this limit is reached within a request, the DeltaQueue must be emptied by several successive DeltaRequests. We recommend, however, to try not to reach that limit but trigger the fetching of data from the connected BWs already when the number of LUWs reaches a 5-digit value.
Q) I would like to display the date the data was uploaded on the report. Usually, we load the transactional data nightly. Is there any easy way to include this information on the report for users? So that they know the validity of the report.
A) If I understand your requirement correctly, you want to display the date on which data was loaded into the data target from which the report is being executed. If it is so, configure your workbook to display the text elements in the report. This displays the relevance of data field, which is the date on which the data load has taken place.
Q) Can we filter the fields at Transfer Structure?
Q) Can we load data directly into infoobject with out extraction is it possible.
Yes. We can copy from other infoobject if it is same. We load data from PSA if it is already in PSA.
Q) HOW MANY DAYS CAN WE KEEP THE DATA IN PSA, IF WE R SHEDULED DAILY, WEEKLY AND MONTHLY.
a) We can set the time.
Q) HOW CAN U GET THE DATA FROM CLIENT IF U R WORKING ON OFFSHORE PROJECTS. THROUGH WHICH NETWORK.
a) VPN .Virtual Private Network, VPN is nothing but one sort of network where we can connect to the client systems sitting in offshore through RAS (Remote access server).
Q) HOW CAN U ANALIZE THE PROJECT AT FIRST?
Prepare Project Plan and Environment
Define Project Management Standards and
Procedures
Define Implementation Standards and Procedures
Testing & Go-live + supporting.
Q) THERE is one ODS AND 4 INFOCUBES. WE SEND DATA AT TIME TO ALL CUBES IF ONE CUBE GOT LOCK ERROR. HOW CAN U RECTIFY THE ERROR?
Go to TCode sm66 then see which one is locked select that pid from there and goto sm12
TCode then unlock it this is happened when lock errors are occurred when u scheduled.
Q) Can anybody tell me how to add a navigational attribute in the BEx report in the rows?
A) Expand dimension under left side panel (that is infocube panel) select than navigational attributes drag and drop under rows panel.
Q) IF ANY TRASACTION CODE LIKE SMPT OR STMT.
In current systems (BW 3.0B and R/3 4.6B) these Tcodes don't exist!
Q) WHAT IS TRANSACTIONAL CUBE?
A) Transactional InfoCubes differ from standard InfoCubes in that the former have an improved write access performance level. Standard InfoCubes are technically optimized for read-only access and for a comparatively small number of simultaneous accesses. Instead, the transactional InfoCube was developed to meet the demands of SAP Strategic Enterprise Management (SEM), meaning that, data is written to the InfoCube (possibly by several users at the same time) and re-read as soon as possible. Standard Basic cubes are not suitable for this.
Q) Is there any way to delete cube contents within update rules from an ODS data source? The reason for this would be to delete (or zero out) a cube record in an "Open Order" cube if the open order quantity was 0.
I've tried using the 0recordmode but that doesn't work. Also, would it
be easier to write a program that would be run after the load and delete
the records with a zero open qty?
A) START routine for update rules u can write ABAP code.
A) Yap, you can do it. Create a start routine in Update rule.
It is not "Deleting cube contents with update rules" It is only possible to avoid that some content is updated into the InfoCube using the start routine. Loop at all the records and delete the record that has the condition. "If the open order quantity was 0" You have to think also in before and after images in case of a delta upload. In that case you may delete the change record and keep the old and after the change the wrong information.
Q) I am not able to access a node in hierarchy directly using variables for reports. When I am using Tcode RSZV it is giving a message that it doesn't exist in BW 3.0 and it is embedded in BEx. Can any one tell me the other options to get the same functionality in BEx?
A) Tcode RSZV is used in the earlier version of 3.0B only. From 3.0B onwards, it's possible in the Query Designer (BEx) itself. Just right click on the InfoObject for which you want to use as variables and precede further selecting variable type and processing types.
Q) Wondering how can I get the values, for an example, if I run a report for month range 01/2004 - 10/2004 then monthly value is actually divide by the number of months that I selected. Which variable should I use?
Q) Why is it every time I switch from Info Provider to InfoObject or from one item to another while in modeling I always get this message " Reading Data " or "constructing workbench" in it runs for minutes.... anyway to stop this?
Q) Can any one give me info on how the BW delta works also would like to know about 'before image and after image' am currently in a BW project and have to write start routines for delta load.
Q) I am very new to BW. I would like to clarify a doubt regarding Delta extractor. If I am correct, by using delta extractors the data that has already been scheduled will not be uploaded again. Say for a specific scenario, Sales. Now I have uploaded all the sales order created till yesterday into the cube. Now say I make changes to any of the open record, which was already uploaded. Now what happens when I schedule it again? Will the same record be uploaded again with the changes or will the changes get affected to the previous record.
A)
Q) In BW we need to write abap routines. I wish to know when and what type of abap routines we got to write. Also, are these routines written in update rules? I will be glad, if this is clarified with real-time scenarios and few examples?
A) Over here we write our routines in the start routines in the update rules or in the transfer structure (you can choose between writing them in the start routines or directly behind the different characteristics. In the transfer structure you just click on the yellow triangle behind a characteristic and choose "routine". In the update rules you can choose "start routine" or click on the triangle with the green square behind an individual characteristic. Usually we only use start routine when it does not concern one single characteristic (for example when you have to read the same table for 4 characteristics). I hope this helps.
We used ABAP Routines for example:
To convert to Uppercase (transfer structure)
To convert Values out of a third party tool with different keys into the same keys as our SAP System uses (transfer structure)
To select only a part of the data for from an infosource updating the InfoCube (Start Routine) etc.
Q) What is ODS?
A) An ODS object acts as a storage location for consolidated and cleaned-up transaction data (transaction data or master data, for example) on the document (atomic) level.
This data can be evaluated using a BEx query.
Standard ODS Object
Transactional ODS object:
The data is immediately available here for reporting. For implementation, compare with the Transactional ODS Object.
A transactional ODS object differs from a standard ODS object in the way it prepares data. In a standard ODS object, data is stored in different versions ((new) delta, active, (change log) modified), where as a transactional ODS object contains the data in a single version. Therefore, data is stored in precisely the same form in which it was written to the transactional ODS object by the application. In BW, you can use a transaction ODS object as a data target for an analysis process.
The transactional ODS object is also required by diverse applications, such as SAP Strategic Enterprise Management (SEM) for example, as well as other external applications.
Transactional ODS objects allow data to be available quickly. The data from this kind of ODS object is accessed transactionally, that is, data is written to the ODS object (possibly by several users at the same time) and reread as soon as possible.
It offers no replacement for the standard ODS object. Instead, an additional function displays those that can be used for special applications.
The transactional ODS object simply consists of a table for active data. It retrieves its data from external systems via fill- or delete- APIs. The loading process is not supported by the BW system. The advantage to the way it is structured is that data is easy to access. They are made available for reporting immediately after being loaded.
Q) What does InfoCube contains?
A) Each InfoCube has one FactTable & a maximum of 16 (13+3 system defined, time, unit & data packet) dimensions.
Q) What does FACT Table contain?
A FactTable consists of KeyFigures.
Each Fact Table can contain a maximum of 233 key figures.
Dimension can contain up to 248 freely available characteristics.
Q) How many dimensions are in a CUBE?
A) 16 dimensions. (13 user defined & 3 system pre-defined )
Q) What does SID Table contain?
SID keys linked with dimension table & master data tables (attributes, texts, hierarchies)
Q) What does ATTRIBUTE Table contain?
Master attribute data
Q) What does TEXT Table contain?
Master text data, short text, long text, medium text & language key if it is language dependent
Q) What does Hierarchy table contain?Hi DST
This is a great effort and gesture. thank you on behalf of all the newbies.
PJ -
The report l runs very night and gets ended with error
Dear all,
I am facing a problem in solution manger. There is an report (Program/Command RDSMOPSOL_MONIREFRESH ) will runs very night and get ended with error and there is Run-time error "MESSAGE_TYPE_X".
Please suggest how to solve the problem.
Is this report is necessary for the system because it is not mention in the sap stand jobs.
SM37 log
Job started
Step 001 started (program RDSMOPSOL_MONIREFRESH, variant &0000000000875, user ID BASIS)
Opening and closing session started. Session SM2000000000065
Opening and closing the session was successful. Session: SM2000000000065
Opening and closing session started. Session SM2000000000005
ABAP/4 processor: MESSAGE_TYPE_X
Job cancelled
SM:CSA SESSION REFRESH
No. Program/Command Prog. type Spool list Parameter User Lang.
1 RDSMOPSOL_MONIREFRESH ABAP &0000000000876 BASIS EN
Sm21 log
00:00:50 DIA 00 000 SAPSYS EEA OPERATION MODES: Switch to operation mode Normal triggered
00:30:57 BTC 08 200 BASIS R68 Perform rollback
00:30:57 BTC 08 200 BASIS AB0 Run-time error "MESSAGE_TYPE_X" occurred
00:30:57 BTC 08 200 BASIS AB1 > Short dump "081112 003057 sapsm BASIS " generated
00:30:57 BTC 08 200 BASIS D01 Transaction Canceled 00 671 ( MESSAGE_TYPE_X 20081112003057sapsm BASIS 2001 )
00:30:57 BTC 08 200 BASIS R68 Perform rollback
00:30:57 BTC 08 200 BASIS AB0 Run-time error "MESSAGE_TYPE_X" occurred
Details
Recording at local and central time........................ 12.11.2008 00:30:57
Task................ 05312 . 08 B8 BTC background processor No. 08
User................ BASIS
Client.............. 200
Terminal............
Session............. 1
Transaction code....
Program name........
Problem class....... T Transaction Problem
Development class... SABP
Further details for this message type
Module name......... abdynpro
Line................ 1133
Error text.......... ab_jmess
Documentation for system log message AB 0 :
The specified runtime error has occurred in the system.
Parameter
a.. MESSAGE_TYPE_X
Technical details
File................ 000048
Position............ 0000253620
Entry type.......... l ( Error (Module, Row) )
Message ID.......... AB 0
Variable parts...... ab_jmess abdynpro1133
Time Ty. Nr Cl. User Tcod MNo Text Date : 12.11.08
00:30:57 BTC 08 200 BASIS AB1 > Short dump "081112 003057 sapsm BASIS " generated
etails
ecording at local and central time........................ 12.11.2008 00:30:57
ask................ 05312 . 08 B8 BTC background processor No. 08
ser................ BASIS
lient.............. 200
erminal............
ession............. 1
ransaction code....
rogram name........
roblem class....... K SAP Web AS Problem
evelopment class... SABP
BAP Mini dump
ate................ 20081112
ime................ 003057
ost................ sapsm
ser................ BASIS
ocumentation for system log message AB 1 :
A short dump was generated for the specified program termination.
You can analyze this short dump in the system log evaluation by
selecting this line or evaluating Table SNAP (Transaction ST22).
echnical details
ile................ 000048
osition............ 0000253800
ntry type.......... s ( ABAP Runtime Error )
essage ID.......... AB 1
ariable parts...... 081112003057sapsm BASIS
Time Ty. Nr Cl. User Tcod MNo Text Date : 12.11.08
00:30:57 BTC 08 200 BASIS D01 Transaction Canceled 00 671 ( MESSAGE_TYPE_X 20081112003057sapsm BASIS 2001 )
Details
Recording at local and central time........................ 12.11.2008 00:30:57
Task................ 05312 . 08 B8 BTC background processor No. 08
User................ BASIS
Client.............. 200
Terminal............
Session............. 1
Transaction code....
Program name........
Problem class....... K SAP Web AS Problem
Development class... SDYN
Module name.........
Location............
T100................ 00 671
Parameters..........
Documentation for system log message D0 1 :
The transaction has been terminated. This may be caused by a
termination message from the application (MESSAGE Axxx) or by an
error detected by the SAP System due to which it makes no sense to
proceed with the transaction. The actual reason for the termination
is indicated by the T100 message and the parameters.
Additional documentation for message 00 671
ABAP/4 processor: &
No documentation exists for message 00671
Parameter
a.. MESSAGE_TYPE_X
00:30:57 BTC 08 200 BASIS R68 Perform rollback
Details
Recording at local and central time........................ 12.11.2008 00:30:57
Task................ 05312 . 08 B8 BTC background processor No. 08
User................ BASIS
Client.............. 200
Terminal............
Session............. 1
Transaction code....
Program name........
Problem class....... W Warning
Development class... STSK
Further details for this message type
Module name......... thxxhead
Line................ 1240
Error text..........
Caller.............. ThIRoll
Reason/called....... roll ba
Documentation for system log message R6 8 :
An error has causes an SAP rollback. All database updates are reset.
Technical details
File................ 000048
Position............ 0000254520
Entry type.......... m ( Error (Function,Module,Row) )
Message ID.......... R6 8
Variable parts...... ThIRollroll bathxxhead1240
Regards,
ShivaHi karteek,
I have check there is Switch of operation mode but when I have checked the t-code sm63 there is no new mode are in normal mode.
There is one thing I want to ask dose this report (Program/Command RDSMOPSOL_MONIREFRESH ) run in your system or any one server because I have think there is some problem in job shued
and is also not mention in the sap stand jobs.
there is an error in sm21 in job.
BASIS SM36 EFK BP_CHECK_REPORT_VALUES: Invalid program values found. Reason:
BASIS SM36 EFC > Program RDSMOPSOL_MONIREFRESH has no variants, but a variant was specified
Is this SM37 log
Job started
Step 001 started (program RDSMOPSOL_MONIREFRESH, variant &0000000000875, user ID BASIS)
Opening and closing session started. Session SM2000000000065
Opening and closing the session was successful. Session: SM2000000000065
Opening and closing session started. Session SM2000000000005
ABAP/4 processor: MESSAGE_TYPE_X
Job cancelled
Sm21 log
SAPSYS EEA OPERATION MODES: Switch to operation mode Normal triggered
BASIS R68 Perform rollback
BASIS AB0 Run-time error "MESSAGE_TYPE_X" occurred
BASIS AB1 > Short dump "081111 003056 sapsm BASIS " generated
BASIS D01 Transaction Canceled 00 671 ( MESSAGE_TYPE_X 20081111003056sapsm BASIS 2001 )
BASIS R68 Perform rollback
BASIS R49 Communication error, CPIC return code 017, SAP return code 223
BASIS R64 > CPI-C function: CMINIT(SAP)
*BASIS SM36 EFK BP_CHECK_REPORT_VALUES: Invalid program values found. Reason:*
*BASIS SM36 EFC > Program RDSMOPSOL_MONIREFRESH has no variants, but a variant was*
specified
BASIS R68 Perform rollback
BASIS AB0 Run-time error "MESSAGE_TYPE_X" occurred
BASIS AB1 > Short dump "081111 220948 sapsm BASIS " generated
BASIS D01 Transaction Canceled 00 671 ( MESSAGE_TYPE_X 20081111220948sapsm BASIS 2001 )
Details Page 2 Line 6 System Log: Local Analysis of sapsm 1
Time Ty. Nr Cl. User Tcod MNo Text
00:00:51 DIA 00 000 SAPSYS EEA OPERATION MODES: Switch to operation mode Normal triggered
Details
Recording at local and central time........................ 13.11.2008 00:00:51
Task................ 04100 . 00 D0 Dialog work process No. 00
User................ SAPSYS
Client.............. 000
Terminal............
Session............. 1
Transaction code....
Program name........
Problem class....... S Operation Trace
Development class... SBTC
Sm63
Start/end time Name of the active operation mode
00.00 - 01.00 Normal
01.00 - 02.00 Normal
02.00 - 03.00 Normal
03.00 - 04.00 Normal
04.00 - 05.00 Normal
05.00 - 06.00 Normal
06.00 - 07.00 Normal
07.00 - 08.00 Normal
08.00 - 09.00 Normal
09.00 - 10.00 Normal
10.00 - 11.00 Normal
11.00 - 12.00 Normal
12.00 - 13.00 Normal
13.00 - 14.00 Normal
14.00 - 15.00 Normal
15.00 - 16.00 Normal
16.00 - 17.00 Normal
17.00 - 18.00 Normal
18.00 - 19.00 Normal
19.00 - 20.00 Normal
20.00 - 21.00 Normal
21.00 - 22.00 Normal
22.00 - 23.00 Normal
23.00 - 00.00 Normal
Regards, -
Getting short dumps while reading bulky data from excel sheet
Hi all,
We have converted our non-unicode based sap system (R/3 4.7, Windows 2003,
SQL 2000) into a unicode based system recently. We are facing two peculiar
problems for last few days.
*Problem 1 - *Whenever we want to upload the data from excel sheet, the
system throws a dump after reading about 400 entries, while last week the
same system used to read about 8000 entries in a single go.
*Problem 2 - *Also, whenever we realease a transport requst from development
containing a lot of changes, the request will reach the quality system but
without the changes. but if i ll try to import the changes into quality
system after generating more than one request containing small small
changes, they get reflected in QAS immediately. Is there any size
constraint in transporting a request fro DEV->QAS->PRD.
Please suggest some ways.
I am pasting the dump (that I am getting while data uploading from Excel).
~~~~~~~~~~~~~~~~~~
Runtime errors
MESSAGE_TYPE_X*
Occurred on
22.02.2008 at
13:21:02*
The current application triggered a termination with a short dump.
What happened?
The current application program detected a situation which really
should not occur. Therefore, a termination with a short dump was
triggered on purpose by the key word MESSAGE (type X).
What can you do?
Print out the error message (using the "Print" function)
and make a note of the actions and input that caused the
error.
To resolve the problem, contact your SAP system administrator.
You can use transaction ST22 (ABAP Dump Analysis) to view and administer
termination messages, especially those beyond their normal deletion
date.
Error analysis
Short text of error message:
Control Framework : Error processing control
Technical information about the message:
Diagnosis
An error occurred when the system tried to process the commands
from the Automation Queue on the presentation server.
There are several possible reasons for this:
- The installation of the SAP GUI on the presentation server is
faulty or obsolete.
- There is an error in the application program
- There is an error in the SAPGUI or an integrated control
Procedure
1. Make sure that you have imported the appropriate Support
Package, the current kernel, and GUI patch for the release of your
System
2. Check whether the error occurs locally on one or a few PCs, or
generally on all PCs. Note whether the error only occurs for some
users, for example because of a specific Customizing setting.
If it only occurs locally, this suggests an installation problem
with the PC. Check the installation; if necessary, reinstall the
software. In the dump, search for the SY-MSGLI field, since it may
point to the cause of the error.
3. Activate the Automation Trace (in accordance with SAP Note
158985).
4.Start the transaction and continue until the screen immediately
before the dump.
5. From the System -> Utilities menu, choose Autom. Queue,
Synchronous Processing.
The status bar of the GUI displays the text:
"Automation synchron flush mode on"
6. If you now proceed with the application, the short dump will
display the ABAP call that caused the error; the Automation Trace
will contain the error on the presentation server.
7. If necessary, load the short dump and trace files on to
sapservX, so that SAP can analyze them.
Message classe...... "CNDP"
Number.............. 006
Variable 1.......... " "
Variable 2.......... " "
Variable 3.......... " "
Variable 4.......... " "
Variable 3.......... " "
Variable 4.......... " "
How to correct the error
Probably the only way to eliminate the error is to correct the program.
You may able to find an interim solution to the problem
in the SAP note system. If you have access to the note system yourself,
use the following search criteria:
"MESSAGE_TYPE_X" C
"SAPLOLEA" or "LOLEAU02"
"AC_SYSTEM_FLUSH"
If you cannot solve the problem yourself, please send the
following documents to SAP:
1. A hard copy print describing the problem.
To obtain this, select the "Print" function on the current screen.
2. A suitable hardcopy prinout of the system log.
To obtain this, call the system log with Transaction SM21
and select the "Print" function to print out the relevant
part.
3. If the programs are your own programs or modified SAP programs,
supply the source code.
To do this, you can either use the "PRINT" command in the editor or
print the programs using the report RSINCL00.
4. Details regarding the conditions under which the error occurred
or which actions and input led to the error.
System environment
SAP Release.............. "620"
Application server....... "nhbho930"
Network address.......... "192.168.0.30"
Operating system......... "Windows NT"
Release.................. "5.2"
Hardware type............ "4x Intel 801586"
Character length......... 16 Bits
Pointer length........... 32 Bits
Work process number...... 0
Short dump setting....... "full"
Database server.......... "NHBHO930"
Database type............ "MSSQL"
Database name............ "DEV"
Database owner........... "dev"
Character set............ "C"
SAP kernel............... "640"
Created on............... "Aug 17 2007 00:18:58"
Created in............... "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"
Database version......... "SQL_Server_8.00 "
Patch level.............. "196"
Patch text............... " "
Supported environment....
Database................. "MSSQL 7.00.699 or higher, MSSQL 8.00.194"
SAP database version..... "640"
Operating system......... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2,
Windows NT 6.0"
User, transaction...
Client.............. 300
User................ "NHBABAP"
Language key........ "E"
Transaction......... "SE38 "
Program............. "SAPLOLEA"
Screen.............. "SAPMSDYP 0010"
Screen line......... 0
Information on where terminated
The termination occurred in the ABAP program "SAPLOLEA" in
"AC_SYSTEM_FLUSH".
The main program was "ZBDC_CONTRACT ".
The termination occurred in line 29 of the source code of the (Include)
program "LOLEAU02"
of the source code of program "LOLEAU02" (when calling the editor 290).
~~~~~~~~~~~~~~~~~~~~~
Thank you all.
Cheers.
Mitra __.____._for the 50 millionth time: Excel spreadsheets are NOT databases, you should NOT try to use them as such and NEVER access them using JDBC.
You should also under NO condition use the JDBC-ODBC bridge driver (that was actually the 78 millionth time that was told someone). -
Hy Gurus
I am new to BW.
Can u please let me know the answers for the following Qs.
1. What is a Data warehouse? List Few Properties of a Data warehouse.
2. What are the major challenges of any Data Warehouse design?
3. Data loading issues, Reporting, Production support issues?
4. Data Modeling, Info cube, ODS obj creation?
5. SAP Batch process in BW side?
6. How to schedule the Background jobs in ABAP, & BW?
7. Variables in Query? User exit variables? How do u create user exit variable? And wt u have used?
8. Structures in Query Reporting? What are structures?
9. Transportation steps?
10. How to compress the Info cube? What happens when you compress the info cube?
11. Performance issues in Reporting? How can you improve the performance of the query?
12. Where the ABAP routines are used in BW side?
13. How to create Primary index & secondary indexes on ODS?
14. How to prevent the duplicate records at the data target level?
15. Issues regarding double records?
16. Info sets and multiprovider differences?
17. Issues faced in Delta loading? Why it happened?
Enhancements to the Data sources?
18. Issues in loading the data from Flat files? Delta load issues? Which will u suggest for flat file loading is it delta or full load?
19. How to prevent the Replication Errors? What happens when you replicate the Data Sources?
20. Process chain steps? Which process type is used to delete the last request when loading the data?
21. What is virtual cube? Characteristics? Its significance?
22. Diff. methods for Generic Data Sources?
23. What is Extract structure? Where it is used?
24. Data Modeling design issues, Tech specifications, Modeling , Reporting, Testing, Transportation
25. Extraction on R/3 side steps?LOs
26. How do you setup LIS?
27. SAP Batch process? /.where does u setup batch process?
28. Reconstruction tab in Info cube? Why it is used?
29. Suppose Info cube (A) having 10 records.
We want to take the some records say 4-7 from Info cube (A) -- Info cube (B).
How does u handle the situation?
30. Suppose ODS contains 5 records and the Info cube shows 12 records. How to solve it?
31. Landscape
32. Tell me typical BW Team & How u work?
33. How to Maintain the Master data at Client Server architecture?
34. Query performance problems? How does u improve the performance?
35. How does u improve the Info cube design performance?
36. How do you improve the Dimension & fact table performance?
37. How to push data from PSA to ODS?
38. How to postpone daily load?
39. The functions of Administrator Workbench are
40. What is RECORD MODE
41. What is partition? How to partition the Info cube & PSA. ?..
42. How to filter single records when uploading into an ods object?
43. How can u connect a new data target to an existing data flow?
44. When it is advantageous to create secondary indexes for ODS field?
45. Purpose of setup tables?
46. What is Delta mechanism?
47. Will u create an infosourse for every data souse? How many infosourse can we connect to a Data Sources?
48. What is a Star Schema? What is the Differences between a Classic Star Schema & Extended Star schema.
49. What is an Attribute? Difference between Display Attribute & Navigational Attribute?
50. What is Transfer Rule? List the methods used in Transfer Rules.
51. Why we need ODS? /List a few of the technical settings that can be defined when building/modifying an ODSObject?
52. What is ODS? What are the three tables associated with an ODS object? What are the two types of ODS.
53. Name the two tables that provide detailed information about data sources.
54. What are two data transfer methods? Which is the preferred method and why?
55. Where will the development take place?& Who will do the development testing.
56. Who will be responsible for long-term support?
57. What is a Slowly Changing Dimension?
58. What is namespace for SAP BW?
59. What are nine decision points of Data warehouse
60. How does u install BW Statistics? How you enable monitoring using BW Statistics.
61. How do u rate u r self in Modeling, Reporting & Extraction.
62. What are the advantages with LO Extraction.
63. What are the steps in General to enhance data?
64. What are Phases in ASAP Methodology?
65. What is the 90 Day rule?
66. What is the demo content use?
67. What is the use of RSRAJ Transaction?
68. What is the use of RSSU53 Transaction?
69. Can u repeat the Master Data Source?
70. What is diff. b/w DW and BW?
71. Will u use idol methods in BW?
72. What does the number in the 'Total' column in Transaction RSA7 mean?
73. The extract structure was changed when the Delta Queue was empty. Afterwards new delta records were written to the Delta Queue. When loading the delta into the PSA, it shows that some fields were moved. The same result occurs when the contents of the Delta Queue are listed via the detail display. Why are the data displayed differently? What can be done?
74. How and where can you control whether a repeat delta is requested?
75. Can I use several clients within SAP BW?
Thanks in Advance
muraliHi
I have few questions and answer u can check it out which would be more helpful
Solution
Questions and answers.
Question 1:
What does the number in the 'Total' column in Transaction RSA7 mean?
Answer:
The 'Total' column displays the number of LUWs that were written in the delta queue and that have not yet been confirmed. The number includes the LUWs of the last delta request (for repeating a delta request) and the LUWs for the next delta request. An LUW only disappears from the RSA7 display when it has been transferred to the BW System and a new delta request has been received from the BW System.
Question 2:
What is an LUW in the delta queue?
Answer:
An LUW from the point of view of the delta queue can be an individual document, a group of documents from a collective run or a whole data packet from an application extractor.
Question 3:
Why does the number in the 'Total' column, in the overview screen of Transaction RSA7, differ from the number of data records that are displayed when you call up the detail view?
Answer:
The number on the overview screen corresponds to the total number of LUWs (see also question 1) that were written to the qRFC queue and that have not yet been confirmed. The detail screen displays the records contained in the LUWs. Both the records belonging to the previous delta request and the records that do not meet the selection conditions of the preceding delta init requests are filtered out. This means that only the records that are ready for the next delta request are displayed on the detail screen. The detail screen of Transaction RSA7 does not take into account a possibly existing customer exit.
Question 4:
Why does Transaction RSA7 still display LUWs on the overview screen after successful delta loading?
Answer:
Only when a new delta has been requested does the source system learn that the previous delta was successfully loaded into the BW System. The LUWs of the previous delta may then be confirmed (and also deleted). In the meantime, the LUWs must be kept for a possible delta request repetition. In particular, the number on the overview screen does not change if the first delta is loaded into the BW System.
Question 5:
Why are selections not taken into account when the delta queue is filled?
Answer:
Filtering according to selections takes place when the system reads from the delta queue. This is necessary for performance reasons.
Question 6:
Why is there a DataSource with '0' records in RSA7 if delta exists and has been loaded successfully?
Answer:
It is most likely that this is a DataSource that does not send delta data to the BW System via the delta queue but directly via the extractor . You can display the current delta data for these DataSources using TA RSA3 (update mode ='D')
Question 7:
Do the entries in Table ROIDOCPRMS have an impact on the performance of the loading procedure from the delta queue?
Answer:
The impact is limited. If performance problems are related to the loading process from the delta queue, then refer to the application-specific notes (for example in the CO-PA area, in the logistics cockpit area, and so on).
Caution: As of PlugIn 2000.2 patch 3, the entries in Table ROIDOCPRMS are as effective for the delta queue as for a full update. Note, however, that LUWs are not split during data loading for consistency reasons. This means that when very large LUWs are written to the delta queue, the actual package size may differ considerably from the MAXSIZE and MAXLINES parameters.
Question 8:
Why does it take so long to display the data in the delta queue (for example approximately 2 hours)?
Answer:
With PlugIn 2001.1 the display was changed: you are now able to define the amount of data to be displayed, to restrict it, to selectively choose the number of a data record, to make a distinction between the 'actual' delta data and the data intended for repetition, and so on.
Question 9:
What is the purpose of the function 'Delete Data and Meta Data in a Queue' in RSA7? What exactly is deleted?
Answer:
You should act with extreme caution when you use the delete function in the delta queue. It is comparable to deleting an InitDelta in the BW System and should preferably be executed there. Not only do you delete all data of this DataSource for the affected BW System, but you also lose all the information concerning the delta initialization. Then you can only request new deltas after another delta initialization.
When you delete the data, this confirms the LUWs kept in the qRFC queue for the corresponding target system. Physical deletion only takes place in the qRFC outbound queue if there are no more references to the LUWs.
The delete function is intended for example, for cases where the BW System, from which the delta initialization was originally executed, no longer exists or can no longer be accessed.
Question 10:
Why does it take so long to delete from the delta queue (for example half a day)?
Answer:
Import PlugIn 2000.2 patch 3. With this patch the performance during deletion improves considerably.
Question 11:
Why is the delta queue not updated when you start the V3 update in the logistics cockpit area?
Answer:
It is most likely that a delta initialization had not yet run or that the the delta initialization was not successful. A successful delta initialization (the corresponding request must have QM status 'green' in the BW System) is a prerequisite for the application data to be written to the delta queue.
Question 12:
What is the relationship between RSA7 and the qRFC monitor (Transaction SMQ1)?
Answer:
The qRFC monitor basically displays the same data as RSA7. The internal queue name must be used for selection on the initial screen of the qRFC monitor. This is made up of the prefix 'BW, the client and the short name of the DataSource. For DataSources whose name is shorter than 20 characters, the short name corresponds to the name of the DataSource. For DataSources whose name is longer than 19 characters (for delta-capable DataSources only possible as of PlugIn 2001.1) the short name is assigned in Table ROOSSHORTN.
In the qRFC monitor you cannot distinguish between repeatable and new LUWs. Moreover, the data of a LUW is displayed in an unstructured manner there.
Question 13:
Why is there data in the delta queue although the V3 update has not yet been started?
Answer:
You posted data in the background. This means that the records are updated directly in the delta queue (RSA7). This happens in particular during automatic goods receipt posting (MRRS). There is no duplicate transfer of records to the BW system. See Note 417189.
Question 14:
Why does the 'Repeatable' button on the RSA7 data details screen not only show data loaded into BW during the last delta but also newly-added data, in other words, 'pure' delta records?
Answer:
It was programmed so that the request in repeat mode fetches both actually repeatable (old) data and new data from the source system.
Question 15:
I loaded several delta inits with various selections. For which one
is the delta loaded?
Answer:
For delta, all selections made via delta inits are summed up. This
means a delta for the 'total' of all delta initializations is loaded.
Question 16:
How many selections for delta inits are possible in the system?
Answer:
With simple selections (intervals without complicated join conditions or single values), you can make up to about 100 delta inits. It should not be more.
With complicated selection conditions, it should be only up to 10-20 delta inits.
Reason: With many selection conditions that are joined in a complicated way, too many 'where' lines are generated in the generated ABAP source code which may exceed the memory limit.
Question 17:
I intend to copy the source system, i.e. make a client copy. What will happen with may delta? Should I initialize again after that?
Answer:
Before you copy a source client or source system, make sure that your deltas have been fetched from the delta queue into BW and that no delta is pending. After the client copy, an inconsistency might occur between BW delta tables and the OLTP delta tables as described in Note 405943. After the client copy, Table ROOSPRMSC will probably be empty in the OLTP since this table is client-independent. After the system copy, the table will contain the entries with the old logical system name which are no longer useful for further delta loading from the new logical system. The delta must be initialized in any case since delta depends on both the BW system and the source system. Even if no dump 'MESSAGE_TYPE_X' occurs in BW when editing or creating an InfoPackage, you should expect that the delta has to be initialized after the copy.
Question 18.
Am I permitted to use the functions in Transaction SMQ1 to manually control processes?
Answer:
Use SMQ1 as an instrument for diagnosis and control only. Make changes to BW queues only after informing BW Support or only if this is explicitly requested in a note for Component 'BC-BW' or 'BW-WHM-SAPI'.
Question 19.
Despite the delta request only being started after completion of the collective run (V3 update), it does not contain all documents. Only another delta request loads the missing documents into BW. What is the cause for this "splitting"?
Answer:
The collective run submits the open V2 documents to the task handler for processing. The task handler processes them in one or several parallel update processes in an asynchronous way. For this reason, plan a sufficiently large "safety time window" between the end of the collective run in the source system and the start of the delta request in BW. An alternative solution where this problem does not occur is described in Note 505700.
Question 20.
Despite deleting the delta init, LUWs are still written into the DeltaQueue
Answer:
In general, delta initializations and deletions of delta inits should always be carried out at a time when no posting takes place. Otherwise, buffer problems may occur: If you started the internal mode at a time when the delta initialization was still active, you post data into the queue even though the initialization had been deleted in the meantime. This is the case in your system.
Question 21.
In SMQ1 (qRFC Monitor) I have status 'NOSEND'. In the Table TRFCQOUT, some entries have the status 'READY', others 'RECORDED'. ARFCSSTATE is 'READ'. What do these statuses mean? Which values in the field 'Status' mean what and which values are correct and which are alarming? Are the statuses BW-specific or generally valid in qRFC?
Answer:
Table TRFCQOUT and ARFCSSTATE: Status READ means that the record was read once either in a delta request or in a repetition of the delta request. However, this still does not mean that the record has successfully reached the BW. The status READY in the TRFCQOUT and RECORDED in the ARFCSSTATE means that the record has been written into the delta queue and will be loaded into the BW with the next delta request or a repetition of a delta. In any case only the statuses READ, READY and RECORDED in both tables are considered to be valid. The status EXECUTED in TRFCQOUT can occur temporarily. It is set before starting a delta extraction for all records with status READ present at that time. The records with status EXECUTED are usually deleted from the queue in packages within a delta request directly after setting the status before extracting a new delta. If you see such records, it means that either a process which confirms and deletes records loaded into the BW is successfully running at the moment, or, if the records remain in the table for a longer period of time with status EXECUTED, it is likely that there are problems with deleting the records which have already been successfully been loaded into the BW. In this state, no more deltas are loaded into the BW. Every other status indicates an error or an inconsistency. NOSEND in SMQ1 means nothing (see note 378903). However the value 'U' in field 'NOSEND' of table TRFCQOUT is of concern.
Question 22.
The extract structure was changed when the delta queue was empty. Afterwards new delta records were written to the delta queue. When loading the delta into the PSA, it shows that some fields were moved. The same result occurs when the contents of the delta queue are listed via the detail display. Why is the data displayed differently? What can be done?
Answer:
Make sure that the change of the extract structure is also reflected in the database and that all servers are synchronized. We recommend resetting the buffers using Transaction $SYNC. If the extract structure change is not communicated synchronously to the server where delta records are being created, the records are written with the old structure until the new structure has been generated. This may have disastrous consequences for the delta. When the problem occurs, the delta needs to be re-initialized.
Question 23. How and where can I control whether a repeat delta is requested?
Answer:
Via the status of the last delta in the BW Request Monitor. If the request is RED, the next load will be of type 'Repeat'. If you need to repeat the last load for any reason, manually set the request in the monitor to red. For the contents of the repeat, see Question 14. Delta requests set to red when data is already updated lead to duplicate records in a subsequent repeat, if they have not already been deleted from the data targets concerned.
Question 24.
As of PI 2003.1, the Logistic Cockpit offers various types of update methods. Which update method is recommended in logistics? According to which criteria should the decision be made? How can I choose an update method in logistics?
Answer:
See the recommendation in Note 505700.
Question 25.
Are there particular recommendations regarding the maximum data volume of the delta queue to avoid danger of a read failure due to memory problems?
Answer:
There is no strict limit (except for the restricted number area of the 24-digit QCOUNT counter in the LUW management table - which is of no practical importance, however - or the restrictions regarding the volume and number of records in a database table).
When estimating "soft" limits, both the number of LUWs and the average data volume per LUW are important. As a rule, we recommend bundling data (usually documents) as soon as you write to the delta queue to keep number of LUWs low (this can partly be set in the applications, for example in the Logistics Cockpit). The data volume of a single LUW should not be much larger than 10% of the memory available to the work process for data extraction (in a 32-bit architecture with a memory volume of about 1 GByte per work process, 100 MByte per LUW should not be exceeded). This limit is of rather small practical importance as well since a comparable limit already applies when writing to the delta queue. If the limit is observed, correct reading is guaranteed in most cases.
If the number of LUWs cannot be reduced by bundling application transactions, you should at least make sure that the data is fetched from all connected BWs as quickly as possible. But for other, BW-specific, reasons, the frequency should not exceed one delta request per hour.
To avoid memory problems, a program-internal limit ensures that no more than 1 million LUWs are ever read and fetched from the database per delta request. If this limit is reached within a request, the delta queue must be emptied by several successive delta requests. We recommend, however, to try not to reach that limit but trigger the fetching of data from the connected BWs as soon as the number of LUWs reaches a 5-digit value.
THANKS =POINTS in SDN
SANJEEV -
Short dump while opening the infopackage............
Hi,
I am getting Short dump. This happens when I am opening any info package for one Infosource. I am not getting any error when I open other infopackages. There are 7 infopackages for this info source and when I open any of these , gets Short Dump with message ...
" The current application program detected a situation which really
should not occur. Therefore, a termination with a short dump was
triggered on purpose by the key word MESSAGE (type X)."
Has any body faced similar problem. Please let me know your ideas on , how to solve this short dump.
Best Regards,
JeetuHi..
When you delete the update status of a request in an InfoCube, short dump
MESSAGE_TYPE_X occurs in program RSBLOGSTATE
You can use the attached program as a correction to check for data inconsistencies and to correct them.
Input parameter:
i_tablnm: ' ' all 'PSA' tables are processed
'/BIC/B......... ' a special table
i_repair: 'X' data with Partno = 0 are corrected.
' ' Check whether data with Partno = 0 exists
i_debug 'X' Activation of default breakpoints
To implement the program, you must create the SAP_PSA_ZEROCORRECT program as an SAP advance correction, leave it empty (Package: RSDD) and then implement it using Transaction SNOTE. Alternatively, you can create the program using the CUT and PASTE method.
If you want to check or correct all tables, you should schedule the program in the background since the runtime (in particular for repairing the tables) may be very long.
In the spool output of the job, you also find the log of the program.
You should first check in check mode whether there is inconsistent data. If this is the case, you must execute the program with i_reapir = 'X'. SAP recommends that you create a variant for the CHECK job and a variant for the REPAIR job. -
SAP MMC changes green to yellow automaticlly
HI experts
recently i installed a ides 5 with oracle 9i,ides is running for a week normally,but yesterday ,SAP MMC suddenly automaticlly changes green to yellow and SAPGUI can't be logged on.
Below is LOG from SAPMMC
Severity Time Typ Client User Tcode MNo Text
2007 12 14 17:32:46 D0 800 LLH R64 SAP Basis System: > CPI-C function: CMINIT(SAP)
Warning 2007 12 14 17:32:46 D0 800 LLH R49 SAP Basis System: Communication error, CPIC return code 027, SAP return code 242
2007 12 14 17:32:23 D0 800 LLH R64 SAP Basis System: > CPI-C function: CMINIT(SAP)
Warning 2007 12 14 17:32:23 D0 800 LLH R49 SAP Basis System: Communication error, CPIC return code 027, SAP return code 242
Error 2007 12 14 17:32:05 RD Q0I SAP Basis System: Operating system call gethostbyaddr failed (error no. 0 )
2007 12 14 17:32:00 D0 800 LLH R64 SAP Basis System: > CPI-C function: CMINIT(SAP)
Warning 2007 12 14 17:32:00 D0 800 LLH R49 SAP Basis System: Communication error, CPIC return code 020, SAP return code -01
2007 12 14 17:31:39 D0 800 LLH R64 SAP Basis System: > CPI-C function: CMINIT(SAP)
Warning 2007 12 14 17:31:39 D0 800 LLH R49 SAP Basis System: Communication error, CPIC return code 020, SAP return code -01
2007 12 14 17:31:18 D0 800 LLH R64 SAP Basis System: > CPI-C function: CMINIT(SAP)
Warning 2007 12 14 17:31:18 D0 800 LLH R49 SAP Basis System: Communication error, CPIC return code 020, SAP return code -01
2007 12 14 17:30:57 D0 800 LLH R64 SAP Basis System: > CPI-C function: CMINIT(SAP)
Warning 2007 12 14 17:30:57 D0 800 LLH R49 SAP Basis System: Communication error, CPIC return code 020, SAP return code -01
2007 12 14 17:30:36 D0 800 LLH R64 SAP Basis System: > CPI-C function: CMINIT(SAP)
Warning 2007 12 14 17:30:36 D0 800 LLH R49 SAP Basis System: Communication error, CPIC return code 020, SAP return code -01
Error 2007 12 14 17:30:18 DP Q04 SAP Basis System: Connection to user 29 ( ), terminal 9 (Amos ) lost
Error 2007 12 14 17:30:18 DP Q0I SAP Basis System: Operating system call recv failed (error no. 10054)
Error 2007 12 14 17:30:14 DP Q0G SAP Basis System: Request (type DIA) cannot be processed
2007 12 14 17:30:13 D0 0 SAPSYS GC4 Operation trace: >>> Profile name = C:\usr\sap\HIS\SYS\profile\HIS_DVEBMGS00_SAPIDES
Warning 2007 12 14 17:30:13 D0 0 SAPSYS GC3 Operation trace: The active profile was modified
Error 2007 12 14 17:30:13 DP Q04 SAP Basis System: Connection to user 16 (HANDSD ), terminal 11 (Amos ) lost
Error 2007 12 14 17:30:13 DP Q0I SAP Basis System: Operating system call gethostbyaddr failed (error no. 0 )
2007 12 14 17:25:14 D0 800 LLH R64 SAP Basis System: > CPI-C function: CMINIT(SAP)
Warning 2007 12 14 17:25:14 D0 800 LLH R49 SAP Basis System: Communication error, CPIC return code 020, SAP return code -01
2007 12 14 17:24:15 D0 800 LLH R64 SAP Basis System: > CPI-C function: CMINIT(SAP)
Warning 2007 12 14 17:24:15 D0 800 LLH R49 SAP Basis System: Communication error, CPIC return code 020, SAP return code -01
2007 12 14 17:23:35 D0 800 LLH R64 SAP Basis System: > CPI-C function: CMINIT(SAP)
Warning 2007 12 14 17:23:35 D0 800 LLH R49 SAP Basis System: Communication error, CPIC return code 020, SAP return code -01
2007 12 14 17:23:14 D0 800 LLH R64 SAP Basis System: > CPI-C function: CMINIT(SAP)
Warning 2007 12 14 17:23:14 D0 800 LLH R49 SAP Basis System: Communication error, CPIC return code 020, SAP return code -01
2007 12 14 17:22:42 D0 800 LLH R64 SAP Basis System: > CPI-C function: CMINIT(SAP)
Warning 2007 12 14 17:22:42 D0 800 LLH R49 SAP Basis System: Communication error, CPIC return code 020, SAP return code -01
2007 12 14 17:22:20 D0 800 LLH R64 SAP Basis System: > CPI-C function: CMINIT(SAP)
Warning 2007 12 14 17:22:20 D0 800 LLH R49 SAP Basis System: Communication error, CPIC return code 027, SAP return code 242
Error 2007 12 14 17:22:20 RD Q0I SAP Basis System: Operating system call SiPeekPendConn failed (error no. 45984)
Error 2007 12 14 17:21:59 RD Q0I SAP Basis System: Operating system call gethostbyaddr failed (error no. 0 )
Error 2007 12 14 17:20:55 B4 0 SAPSYS CP3 SAP Basis System: Character set '8300' does not appear in table 'TCPDB'
2007 12 14 17:20:55 B4 0 SAPSYS CPG SAP Basis System: Failed to Set Environment for Language M Code Page 8300 Locale CHT_TWN.950
Error 2007 12 14 17:20:55 B4 0 SAPSYS CP3 SAP Basis System: Character set '1610' does not appear in table 'TCPDB'
2007 12 14 17:20:55 B4 0 SAPSYS CPG SAP Basis System: Failed to Set Environment for Language T Code Page 1610 Locale Turkish_Turkey.28599
Error 2007 12 14 17:20:55 B4 0 SAPSYS CP3 SAP Basis System: Character set '8600' does not appear in table 'TCPDB'
2007 12 14 17:20:55 B4 0 SAPSYS CPG SAP Basis System: Failed to Set Environment for Language 2 Code Page 8600 Locale Thai_Thailand.874
Error 2007 12 14 17:20:55 B4 0 SAPSYS CP3 SAP Basis System: Character set '1401' does not appear in table 'TCPDB'
2007 12 14 17:20:55 B4 0 SAPSYS CPG SAP Basis System: Failed to Set Environment for Language Q Code Page 1401 Locale Slovak_Slovak.28592
Error 2007 12 14 17:20:55 B4 0 SAPSYS CP3 SAP Basis System: Character set '1500' does not appear in table 'TCPDB'
2007 12 14 17:20:55 B4 0 SAPSYS CPG SAP Basis System: Failed to Set Environment for Language R Code Page 1500 Locale Russian_Russia.28595
Error 2007 12 14 17:20:55 B4 0 SAPSYS CP3 SAP Basis System: Character set '1401' does not appear in table 'TCPDB'
2007 12 14 17:20:55 B4 0 SAPSYS CPG SAP Basis System: Failed to Set Environment for Language L Code Page 1401 Locale Polish_Poland.28592
Error 2007 12 14 17:20:55 B4 0 SAPSYS CP3 SAP Basis System: Character set '8500' does not appear in table 'TCPDB'
2007 12 14 17:20:55 B4 0 SAPSYS CPG SAP Basis System: Failed to Set Environment for Language 3 Code Page 8500 Locale Korean_Korea.949
Error 2007 12 14 17:20:55 B4 0 SAPSYS CP3 SAP Basis System: Character set '8000' does not appear in table 'TCPDB'
2007 12 14 17:20:55 B4 0 SAPSYS CPG SAP Basis System: Failed to Set Environment for Language J Code Page 8000 Locale Japanese_Japan.932
Error 2007 12 14 17:20:55 B4 0 SAPSYS CP3 SAP Basis System: Character set '1401' does not appear in table 'TCPDB'
2007 12 14 17:20:55 B4 0 SAPSYS CPG SAP Basis System: Failed to Set Environment for Language C Code Page 1401 Locale Czech_Czech.28592
Information 2007 12 14 17:20:48 D0 0 SAPSYS A10 SAP Basis System: Initialization complete
Information 2007 12 14 17:20:45 B4 E10 SAP Basis System: Buffer RSCPCCC Generated with Length 6000000
2007 12 14 17:20:43 E3 AV6 Security: Initialization SCSA for Security Audit completed, number of selections 02
Information 2007 12 14 17:20:43 E3 BB0 SAP Basis System: Buffer CALE started with 500000 bytes
Information 2007 12 14 17:20:43 E3 BB0 SAP Basis System: Buffer OTR started with 4096k bytes
Information 2007 12 14 17:20:43 E3 BB0 SAP Basis System: Buffer CUA started with 3000k bytes
Information 2007 12 14 17:20:43 E3 BB0 SAP Basis System: Buffer ESM started with 4096k bytes
Information 2007 12 14 17:20:43 E3 BB0 SAP Basis System: Buffer EIBUF started with 4096k bytes
Information 2007 12 14 17:20:43 E3 BB0 SAP Basis System: Buffer TABLP started with 10240000 bytes
Information 2007 12 14 17:20:43 E3 BB0 SAP Basis System: Buffer TABL started with 30000128 bytes
Information 2007 12 14 17:20:34 W7 Q0Q SAP Basis System: Start Workproc 7, Pid 1628
Information 2007 12 14 17:20:34 W6 Q0Q SAP Basis System: Start Workproc 6, Pid 2604
Information 2007 12 14 17:20:34 W5 Q0Q SAP Basis System: Start Workproc 5, Pid 2844
Information 2007 12 14 17:20:34 W4 Q0Q SAP Basis System: Start Workproc 4, Pid 700
Information 2007 12 14 17:20:34 W3 Q0Q SAP Basis System: Start Workproc 3, Pid 1624
Information 2007 12 14 17:20:34 W2 Q0Q SAP Basis System: Start Workproc 2, Pid 2876
Information 2007 12 14 17:20:34 W1 Q0Q SAP Basis System: Start Workproc 1, Pid 792
Information 2007 12 14 17:20:34 W0 Q0Q SAP Basis System: Start Workproc 0, Pid 2732
Information 2007 12 14 17:20:34 RD S00 Communications data: SAP Gateway Started (PID: 724)
Information 2007 12 14 17:20:33 DP Q1C SAP Basis System: MsgServer Hardware ID Was Determined
Information 2007 12 14 17:20:33 DP Q0K SAP Basis System: Connection to message server (on SAPIDES) established
2007 12 14 17:20:33 DP GZZ SAP Basis System: > 1 possible network problems detected - check tracefile and adjus
Information 2007 12 14 17:20:28 DP Q00 SAP Basis System: R/3 System start, SAPSYSTEM 00, dispatcher PID 3584
Information 2007 12 14 17:20:27 MS Q01 SAP Basis System: Start Msg Server, 1 times since system startup. PID 3580
Information 2007 12 14 17:20:27 MS E10 SAP Basis System: Buffer SCSA Generated with Length 4096
Warning 2007 12 14 17:20:09 MS Q02 SAP Basis System: Stop Msg Server, PID 3940
Information 2007 12 14 17:20:09 DP Q05 SAP Basis System: R/3 System stop, dispatcher PID 39
Error 2007 12 14 17:20:09 DP Q0M SAP Basis System: Message server disconnected
Information 2007 12 14 17:20:06 RD S30 Communications data: SAP gateway was closed
Error 2007 12 14 17:20:05 RD Q0I SAP Basis System: Operating system call recv failed (error no. 10054)
Error 2007 12 14 17:20:05 RD Q0I SAP Basis System: Operating system call recv failed (error no. 10054)
Error 2007 12 14 17:20:05 RD Q0I SAP Basis System: Operating system call recv failed (error no. 10054)
Error 2007 12 14 17:20:05 RD Q0I SAP Basis System: Operating system call recv failed (error no. 10054)
Error 2007 12 14 17:20:05 RD Q0I SAP Basis System: Operating system call recv failed (error no. 10054)
Warning 2007 12 14 17:20:04 D0 Q02 SAP Basis System: Stop Workproc 0, PID 1460
Warning 2007 12 14 17:20:04 D1 Q02 SAP Basis System: Stop Workproc 1, PID 1880
Warning 2007 12 14 17:20:04 E3 Q02 SAP Basis System: Stop Workproc 3, PID 632
Warning 2007 12 14 17:20:04 V7 Q02 SAP Basis System: Stop Workproc 7, PID 1620
Warning 2007 12 14 17:20:04 S6 Q02 SAP Basis System: Stop Workproc 6, PID 1580
Warning 2007 12 14 17:20:04 B5 Q02 SAP Basis System: Stop Workproc 5, PID 1572
Warning 2007 12 14 17:20:04 B4 Q02 SAP Basis System: Stop Workproc 4, PID 1564
Warning 2007 12 14 17:20:04 U2 Q02 SAP Basis System: Stop Workproc 2, PID 1548
2007 12 14 17:15:03 D1 800 LLH R64 SAP Basis System: > CPI-C function: CMINIT(SAP)
Warning 2007 12 14 17:15:03 D1 800 LLH R49 SAP Basis System: Communication error, CPIC return code 027, SAP return code 242
Error 2007 12 14 17:14:45 RD Q0I SAP Basis System: Operating system call gethostbyaddr failed (error no. 0 )
2007 12 14 17:14:40 D1 800 LLH R64 SAP Basis System: > CPI-C function: CMINIT(SAP)
Warning 2007 12 14 17:14:40 D1 800 LLH R49 SAP Basis System: Communication error, CPIC return code 020, SAP return code -01
2007 12 14 17:14:02 D1 800 LLH R64 SAP Basis System: > CPI-C function: CMINIT(SAP)
Warning 2007 12 14 17:14:02 D1 800 LLH R49 SAP Basis System: Communication error, CPIC return code 020, SAP return code -01
2007 12 14 17:13:41 D1 800 LLH R64 SAP Basis System: > CPI-C function: CMINIT(SAP)
Warning 2007 12 14 17:13:41 D1 800 LLH R49 SAP Basis System: Communication error, CPIC return code 020, SAP return code -01
2007 12 14 17:13:01 D1 800 LLH R64 SAP Basis System: > CPI-C function: CMINIT(SAP)
Warning 2007 12 14 17:13:01 D1 800 LLH R49 SAP Basis System: Communication error, CPIC return code 020, SAP return code -01
2007 12 14 17:12:40 D1 800 LLH R64 SAP Basis System: > CPI-C function: CMINIT(SAP)
Warning 2007 12 14 17:12:40 D1 800 LLH R49 SAP Basis System: Communication error, CPIC return code 020, SAP return code -01
2007 12 14 17:12:02 D0 800 LLH R64 SAP Basis System: > CPI-C function: CMINIT(SAP)
Warning 2007 12 14 17:12:02 D0 800 LLH R49 SAP Basis System: Communication error, CPIC return code 020, SAP return code -01
2007 12 14 17:11:40 D1 800 LLH R64 SAP Basis System: > CPI-C function: CMINIT(SAP)
Warning 2007 12 14 17:11:40 D1 800 LLH R49 SAP Basis System: Communication error, CPIC return code 020, SAP return code -01
2007 12 14 17:11:02 D0 800 LLH R64 SAP Basis System: > CPI-C function: CMINIT(SAP)
Warning 2007 12 14 17:11:02 D0 800 LLH R49 SAP Basis System: Communication error, CPIC return code 020, SAP return code -01
2007 12 14 17:10:41 D0 800 LLH R64 SAP Basis System: > CPI-C function: CMINIT(SAP)
Warning 2007 12 14 17:10:41 D0 800 LLH R49 SAP Basis System: Communication error, CPIC return code 020, SAP return code -01
2007 12 14 17:09:40 D0 800 LLH R64 SAP Basis System: > CPI-C function: CMINIT(SAP)
Warning 2007 12 14 17:09:40 D0 800 LLH R49 SAP Basis System: Communication error, CPIC return code 020, SAP return code -01
2007 12 14 17:06:40 D0 800 LLH R64 SAP Basis System: > CPI-C function: CMINIT(SAP)
Warning 2007 12 14 17:06:40 D0 800 LLH R49 SAP Basis System: Communication error, CPIC return code 020, SAP return code -01
2007 12 14 17:06:02 D0 800 LLH R64 SAP Basis System: > CPI-C function: CMINIT(SAP)
Warning 2007 12 14 17:06:02 D0 800 LLH R49 SAP Basis System: Communication error, CPIC return code 020, SAP return code -01
2007 12 14 17:05:41 D0 800 LLH R64 SAP Basis System: > CPI-C function: CMINIT(SAP)
Warning 2007 12 14 17:05:41 D0 800 LLH R49 SAP Basis System: Communication error, CPIC return code 020, SAP return code -01
2007 12 14 17:05:06 D0 800 LLH R64 SAP Basis System: > CPI-C function: CMINIT(SAP)
Warning 2007 12 14 17:05:06 D0 800 LLH R49 SAP Basis System: Communication error, CPIC return code 020, SAP return code -01
2007 12 14 17:04:45 D0 800 LLH R64 SAP Basis System: > CPI-C function: CMINIT(SAP)
Warning 2007 12 14 17:04:45 D0 800 LLH R49 SAP Basis System: Communication error, CPIC return code 027, SAP return code 242
Error 2007 12 14 17:04:24 RD Q0I SAP Basis System: Operating system call gethostbyaddr failed (error no. 0 )
2007 12 14 16:58:26 D1 800 LLH R64 SAP Basis System: > CPI-C function: CMINIT(SAP)
Warning 2007 12 14 16:58:26 D1 800 LLH R49 SAP Basis System: Communication error, CPIC return code 020, SAP return code -01
2007 12 14 16:58:05 D1 800 LLH R64 SAP Basis System: > CPI-C function: CMINIT(SAP)
Warning 2007 12 14 16:58:05 D1 800 LLH R49 SAP Basis System: Communication error, CPIC return code 020, SAP return code -01
2007 12 14 16:57:44 D1 800 LLH R64 SAP Basis System: > CPI-C function: CMINIT(SAP)
Warning 2007 12 14 16:57:44 D1 800 LLH R49 SAP Basis System: Communication error, CPIC return code 020, SAP return code -01
2007 12 14 16:57:23 D1 800 LLH R64 SAP Basis System: > CPI-C function: CMINIT(SAP)
Warning 2007 12 14 16:57:23 D1 800 LLH R49 SAP Basis System: Communication error, CPIC return code 020, SAP return code -01
2007 12 14 16:57:02 D1 800 LLH R64 SAP Basis System: > CPI-C function: CMINIT(SAP)
Warning 2007 12 14 16:57:02 D1 800 LLH R49 SAP Basis System: Communication error, CPIC return code 020, SAP return code -01
2007 12 14 16:56:41 D1 800 LLH R64 SAP Basis System: > CPI-C function: CMINIT(SAP)
Warning 2007 12 14 16:56:41 D1 800 LLH R49 SAP Basis System: Communication error, CPIC return code 020, SAP return code -01
2007 12 14 16:55:34 D0 800 LLH R64 SAP Basis System: > CPI-C function: CMINIT(SAP)
Warning 2007 12 14 16:55:34 D0 800 LLH R49 SAP Basis System: Communication error, CPIC return code 020, SAP return code -01
2007 12 14 16:55:13 D0 800 LLH R64 SAP Basis System: > CPI-C function: CMINIT(SAP)
Warning 2007 12 14 16:55:13 D0 800 LLH R49 SAP Basis System: Communication error, CPIC return code 020, SAP return code -01
2007 12 14 16:54:52 D0 800 LLH R64 SAP Basis System: > CPI-C function: CMINIT(SAP)
Warning 2007 12 14 16:54:52 D0 800 LLH R49 SAP Basis System: Communication error, CPIC return code 020, SAP return code -01
2007 12 14 16:54:31 D0 800 LLH R64 SAP Basis System: > CPI-C function: CMINIT(SAP)
Warning 2007 12 14 16:54:31 D0 800 LLH R49 SAP Basis System: Communication error, CPIC return code 020, SAP return code -01
2007 12 14 16:54:10 D0 800 LLH R64 SAP Basis System: > CPI-C function: CMINIT(SAP)
Warning 2007 12 14 16:54:10 D0 800 LLH R49 SAP Basis System: Communication error, CPIC return code 020, SAP return code -01
Error 2007 12 14 16:53:48 DP Q0G SAP Basis System: Request (type DIA) cannot be processed
2007 12 14 16:53:47 D0 0 SAPSYS GC4 Operation trace: >>> Profile name = C:\usr\sap\HIS\SYS\profile\HIS_DVEBMGS00_SAPIDES
Warning 2007 12 14 16:53:47 D0 0 SAPSYS GC3 Operation trace: The active profile was modified
Error 2007 12 14 16:51:18 DP Q04 SAP Basis System: Connection to user 12 (HANDSD ), terminal 8 (Amos ) lost
Error 2007 12 14 16:51:18 DP Q0I SAP Basis System: Operating system call gethostbyaddr failed (error no. 0 )
2007 12 14 16:50:24 D1 800 LLH R64 SAP Basis System: > CPI-C function: CMINIT(SAP)
Warning 2007 12 14 16:50:24 D1 800 LLH R49 SAP Basis System: Communication error, CPIC return code 020, SAP return code -01
2007 12 14 16:50:03 D1 800 LLH R64 SAP Basis System: > CPI-C function: CMINIT(SAP)
Warning 2007 12 14 16:50:03 D1 800 LLH R49 SAP Basis System: Communication error, CPIC return code 020, SAP return code -01
2007 12 14 16:49:42 D1 800 LLH R64 SAP Basis System: > CPI-C function: CMINIT(SAP)
Warning 2007 12 14 16:49:42 D1 800 LLH R49 SAP Basis System: Communication error, CPIC return code 020, SAP return code -01
2007 12 14 16:49:07 D0 800 LLH R64 SAP Basis System: > CPI-C function: CMINIT(SAP)
Warning 2007 12 14 16:49:07 D0 800 LLH R49 SAP Basis System: Communication error, CPIC return code 020, SAP return code -01
2007 12 14 16:48:44 D0 800 LLH R64 SAP Basis System: > CPI-C function: CMINIT(SAP)
Warning 2007 12 14 16:48:44 D0 800 LLH R49 SAP Basis System: Communication error, CPIC return code 020, SAP return code -01
Error 2007 12 14 16:48:44 RD Q0I SAP Basis System: Operating system call SiPeekPendConn failed (error no. 45984)
Error 2007 12 14 16:48:23 RD Q0I SAP Basis System: Operating system call gethostbyaddr failed (error no. 0 )
Error 2007 12 14 16:48:17 DP Q0G SAP Basis System: Request (type DIA) cannot be processed
Error 2007 12 14 16:47:45 DP Q04 SAP Basis System: Connection to user 14 (WW ), terminal 10 (user34 ) lost
Error 2007 12 14 16:47:44 DP Q0I SAP Basis System: Operating system call recv failed (error no. 10054)
Error 2007 12 14 16:45:42 B4 0 SAPSYS CP3 SAP Basis System: Character set '8300' does not appear in table 'TCPDB'
2007 12 14 16:45:42 B4 0 SAPSYS CPG SAP Basis System: Failed to Set Environment for Language M Code Page 8300 Locale CHT_TWN.950
Error 2007 12 14 16:45:42 B4 0 SAPSYS CP3 SAP Basis System: Character set '1610' does not appear in table 'TCPDB'
2007 12 14 16:45:42 B4 0 SAPSYS CPG SAP Basis System: Failed to Set Environment for Language T Code Page 1610 Locale Turkish_Turkey.28599
Error 2007 12 14 16:45:42 B4 0 SAPSYS CP3 SAP Basis System: Character set '8600' does not appear in table 'TCPDB'
2007 12 14 16:45:42 B4 0 SAPSYS CPG SAP Basis System: Failed to Set Environment for Language 2 Code Page 8600 Locale Thai_Thailand.874
Error 2007 12 14 16:45:42 B4 0 SAPSYS CP3 SAP Basis System: Character set '1401' does not appear in table 'TCPDB'
2007 12 14 16:45:42 B4 0 SAPSYS CPG SAP Basis System: Failed to Set Environment for Language Q Code Page 1401 Locale Slovak_Slovak.28592
Error 2007 12 14 16:45:42 B4 0 SAPSYS CP3 SAP Basis System: Character set '1500' does not appear in table 'TCPDB'
2007 12 14 16:45:42 B4 0 SAPSYS CPG SAP Basis System: Failed to Set Environment for Language R Code Page 1500 Locale Russian_Russia.28595
Error 2007 12 14 16:45:42 B4 0 SAPSYS CP3 SAP Basis System: Character set '1401' does not appear in table 'TCPDB'
2007 12 14 16:45:42 B4 0 SAPSYS CPG SAP Basis System: Failed to Set Environment for Language L Code Page 1401 Locale Polish_Poland.28592
Error 2007 12 14 16:45:42 B4 0 SAPSYS CP3 SAP Basis System: Character set '8500' does not appear in table 'TCPDB'
2007 12 14 16:45:42 B4 0 SAPSYS CPG SAP Basis System: Failed to Set Environment for Language 3 Code Page 8500 Locale Korean_Korea.949
Error 2007 12 14 16:45:42 B4 0 SAPSYS CP3 SAP Basis System: Character set '8000' does not appear in table 'TCPDB'
2007 12 14 16:45:42 B4 0 SAPSYS CPG SAP Basis System: Failed to Set Environment for Language J Code Page 8000 Locale Japanese_Japan.932
Error 2007 12 14 16:45:42 B4 0 SAPSYS CP3 SAP Basis System: Character set '1401' does not appear in table 'TCPDB'
2007 12 14 16:45:42 B4 0 SAPSYS CPG SAP Basis System: Failed to Set Environment for Language C Code Page 1401 Locale Czech_Czech.28592
Information 2007 12 14 16:45:25 D0 0 SAPSYS A10 SAP Basis System: Initialization complete
Information 2007 12 14 16:45:10 S6 E10 SAP Basis System: Buffer RSCPCCC Generated with Length 6000000
2007 12 14 16:45:07 E3 AV6 Security: Initialization SCSA for Security Audit completed, number of selections 02
Information 2007 12 14 16:45:06 E3 BB0 SAP Basis System: Buffer CALE started with 500000 bytes
Information 2007 12 14 16:45:06 E3 BB0 SAP Basis System: Buffer OTR started with 4096k bytes
Information 2007 12 14 16:45:06 E3 BB0 SAP Basis System: Buffer CUA started with 3000k bytes
Information 2007 12 14 16:45:06 E3 BB0 SAP Basis System: Buffer ESM started with 4096k bytes
Information 2007 12 14 16:45:06 E3 BB0 SAP Basis System: Buffer EIBUF started with 4096k bytes
Information 2007 12 14 16:45:05 E3 BB0 SAP Basis System: Buffer TABLP started with 10240000 bytes
Information 2007 12 14 16:45:05 E3 BB0 SAP Basis System: Buffer TABL started with 30000128 bytes
Information 2007 12 14 16:44:59 RD S00 Communications data: SAP Gateway Started (PID: 1416)
Information 2007 12 14 16:44:59 W0 Q0Q SAP Basis System: Start Workproc 0, Pid 1460
Information 2007 12 14 16:44:59 W1 Q0Q SAP Basis System: Start Workproc 1, Pid 1880
Information 2007 12 14 16:44:59 W2 Q0Q SAP Basis System: Start Workproc 2, Pid 1548
Information 2007 12 14 16:44:59 W7 Q0Q SAP Basis System: Start Workproc 7, Pid 1620
Information 2007 12 14 16:44:59 W3 Q0Q SAP Basis System: Start Workproc 3, Pid 632
Information 2007 12 14 16:44:59 W4 Q0Q SAP Basis System: Start Workproc 4, Pid 1564
Information 2007 12 14 16:44:59 W5 Q0Q SAP Basis System: Start Workproc 5, Pid 1572
Information 2007 12 14 16:44:59 W6 Q0Q SAP Basis System: Start Workproc 6, Pid 1580
Information 2007 12 14 16:44:59 DP Q1C SAP Basis System: MsgServer Hardware ID Was Determined
Information 2007 12 14 16:44:59 DP Q0K SAP Basis System: Connection to message server (on SAPIDES) established
2007 12 14 16:44:58 DP GZZ SAP Basis System: > 1 possible network problems detected - check tracefile and adjus
Information 2007 12 14 16:44:53 DP Q00 SAP Basis System: R/3 System start, SAPSYSTEM 00, dispatcher PID 3948
Information 2007 12 14 16:44:53 MS Q01 SAP Basis System: Start Msg Server, 1 times since system startup. PID 3940
Information 2007 12 14 16:44:53 MS E10 SAP Basis System: Buffer SCSA Generated with Length 4096
Warning 2007 12 14 16:37:38 MS Q02 SAP Basis System: Stop Msg Server, PID 2484
Information 2007 12 14 16:37:38 DP Q05 SAP Basis System: R/3 System stop, dispatcher PID 36
Error 2007 12 14 16:37:38 DP Q0M SAP Basis System: Message server disconnected
Information 2007 12 14 16:37:35 RD S30 Communications data: SAP gateway was closed
Warning 2007 12 14 16:37:35 D0 800 CZP Q02 SAP Basis System: Stop Workproc 0, PID 2976
Warning 2007 12 14 16:37:35 D1 800 WW VA01 Q02 SAP Basis System: Stop Workproc 1, PID 3608
2007 12 14 16:37:35 D0 800 CZP R68 SAP Basis System: Perform rollback
Error 2007 12 14 16:37:35 D0 800 CZP R37 SAP Basis System: Error in T100, MSG: 731
Error 2007 12 14 16:37:35 D0 800 CZP R37 SAP Basis System: Error in T100, MSG: 731
2007 12 14 16:37:35 D1 800 WW VA01 R68 SAP Basis System: Perform rollback
Error 2007 12 14 16:37:35 D1 800 WW VA01 R37 SAP Basis System: Error in T100, MSG: 731
Error 2007 12 14 16:37:35 D1 800 WW VA01 R37 SAP Basis System: Error in T100, MSG: 731
2007 12 14 16:37:35 D0 800 CZP R64 SAP Basis System: > CPI-C function: CMRCV
2007 12 14 16:37:35 D0 800 CZP R5A SAP Basis System: > Conversation ID: 21365000
Warning 2007 12 14 16:37:35 D0 800 CZP R49 SAP Basis System: Communication error, CPIC return code 017, SAP return code 731
2007 12 14 16:37:35 D1 800 WW VA01 R64 SAP Basis System: > CPI-C function: CMSEND(SAP)
2007 12 14 16:37:35 D1 800 WW VA01 R5A SAP Basis System: > Conversation ID: 21350000
Warning 2007 12 14 16:37:35 D1 800 WW VA01 R49 SAP Basis System: Communication error, CPIC return code 017, SAP return code 731
Error 2007 12 14 16:36:34 RD Q0I SAP Basis System: Operating system call recv failed (error no. 10054)
Warning 2007 12 14 16:36:34 U2 Q02 SAP Basis System: Stop Workproc 2, PID 3976
Error 2007 12 14 16:36:34 RD Q0I SAP Basis System: Operating system call recv failed (error no. 10054)
Warning 2007 12 14 16:36:34 E3 Q02 SAP Basis System: Stop Workproc 3, PID 1252
Warning 2007 12 14 16:36:34 V7 Q02 SAP Basis System: Stop Workproc 7, PID 2928
Warning 2007 12 14 16:36:34 S6 Q02 SAP Basis System: Stop Workproc 6, PID 3992
Warning 2007 12 14 16:36:34 B4 Q02 SAP Basis System: Stop Workproc 4, PID 2272
Warning 2007 12 14 16:36:34 B5 Q02 SAP Basis System: Stop Workproc 5, PID 2852
2007 12 14 16:36:04 D0 800 LLH R64 SAP Basis System: > CPI-C function: CMINIT(SAP)
Warning 2007 12 14 16:36:04 D0 800 LLH R49 SAP Basis System: Communication error, CPIC return code 020, SAP return code -01
2007 12 14 16:35:42 D1 800 LLH R64 SAP Basis System: > CPI-C function: CMINIT(SAP)
Warning 2007 12 14 16:35:42 D1 800 LLH R49 SAP Basis System: Communication error, CPIC return code 020, SAP return code -01
2007 12 14 16:35:21 D0 800 LLH R64 SAP Basis System: > CPI-C function: CMINIT(SAP)
Warning 2007 12 14 16:35:21 D0 800 LLH R49 SAP Basis System: Communication error, CPIC return code 020, SAP return code -01
2007 12 14 16:35:00 D0 800 LLH R64 SAP Basis System: > CPI-C function: CMINIT(SAP)
Warning 2007 12 14 16:35:00 D0 800 LLH R49 SAP Basis System: Communication error, CPIC return code 020, SAP return code -01
2007 12 14 16:34:37 D1 800 LLH R64 SAP Basis System: > CPI-C function: CMINIT(SAP)
Warning 2007 12 14 16:34:37 D1 800 LLH R49 SAP Basis System: Communication error, CPIC return code 020, SAP return code -01
2007 12 14 16:34:16 D1 800 LLH R64 SAP Basis System: > CPI-C function: CMINIT(SAP)
Warning 2007 12 14 16:34:16 D1 800 LLH R49 SAP Basis System: Communication error, CPIC return code 020, SAP return code -01
2007 12 14 16:33:52 D0 800 LLH R64 SAP Basis System: > CPI-C function: CMINIT(SAP)
Warning 2007 12 14 16:33:52 D0 800 LLH R49 SAP Basis System: Communication error, CPIC return code 027, SAP return code 242
2007 12 14 16:33:26 D0 800 LLH R64 SAP Basis System: > CPI-C function: CMINIT(SAP)
Warning 2007 12 14 16:33:26 D0 800 LLH R49 SAP Basis System: Communication error, CPIC return code 027, SAP return code 242
Error 2007 12 14 16:33:08 RD Q0I SAP Basis System: Operating system call gethostbyaddr failed (error no. 0 )
2007 12 14 16:30:57 D1 800 ZQM VA01 AB1 SAP Basis System: > Short dump "071214 163056 SAPIDES ZQM " generated
Error 2007 12 14 16:30:56 D1 800 ZQM VA01 AB0 SAP Basis System: Run-time error "TIME_OUT " occurred
2007 12 14 16:30:56 D1 800 ZQM VA01 R68 SAP Basis System: Perform rollback
2007 12 14 16:30:56 D0 800 LLH AB1 SAP Basis System: > Short dump "071214 163056 SAPIDES LLH " generated
Error 2007 12 14 16:30:56 D0 800 LLH AB0 SAP Basis System: Run-time error "TIME_OUT " occurred
2007 12 14 16:30:56 D0 800 LLH R68 SAP Basis System: Perform rollback
2007 12 14 16:19:38 D0 800 LLH R64 SAP Basis System: > CPI-C function: CMINIT(SAP)
Warning 2007 12 14 16:19:38 D0 800 LLH R49 SAP Basis System: Communication error, CPIC return code 020, SAP return code -01
2007 12 14 16:19:17 D0 800 LLH R64 SAP Basis System: > CPI-C function: CMINIT(SAP)
Warning 2007 12 14 16:19:17 D0 800 LLH R49 SAP Basis System: Communication error, CPIC return code 020, SAP return code -01
2007 12 14 16:18:56 D0 800 LLH R64 SAP Basis System: > CPI-C function: CMINIT(SAP)
Warning 2007 12 14 16:18:56 D0 800 LLH R49 SAP Basis System: Communication error, CPIC return code 020, SAP return code -01
2007 12 14 16:18:34 D0 800 LLH R64 SAP Basis System: > CPI-C function: CMINIT(SAP)
Warning 2007 12 14 16:18:34 D0 800 LLH R49 SAP Basis System: Communication error, CPIC return code 020, SAP return code -01
2007 12 14 16:18:13 D0 800 LLH R64 SAP Basis System: > CPI-C function: CMINIT(SAP)
Warning 2007 12 14 16:18:13 D0 800 LLH R49 SAP Basis System: Communication error, CPIC return code 020, SAP return code -01
2007 12 14 16:17:52 D0 800 LLH R64 SAP Basis System: > CPI-C function: CMINIT(SAP)
Warning 2007 12 14 16:17:52 D0 800 LLH R49 SAP Basis System: Communication error, CPIC return code 020, SAP return code -01
2007 12 14 16:17:30 D0 800 LLH R64 SAP Basis System: > CPI-C function: CMINIT(SAP)
Warning 2007 12 14 16:17:30 D0 800 LLH R49 SAP Basis System: Communication error, CPIC return code 020, SAP return code -01
2007 12 14 16:17:07 D0 800 LLH R64 SAP Basis System: > CPI-C function: CMINIT(SAP)
Warning 2007 12 14 16:17:07 D0 800 LLH R49 SAP Basis System: Communication error, CPIC return code 027, SAP return code 242
Error 2007 12 14 16:16:46 RD Q0I SAP Basis System: Operating system call gethostbyaddr failed (error no. 0 )
Information 2007 12 14 16:10:35 D1 800 ZJP VA01 R47 SAP Basis System: Delete session 001 after error 061
2007 12 14 16:10:12 D1 800 HJJ AB1 SAP Basis System: > Short dump "071214 161012 SAPIDES HJJ " generated
Error 2007 12 14 16:10:12 D1 800 HJJ AB0 SAP Basis System: Run-time error "MESSAGE_TYPE_X " occurred
2007 12 14 16:10:11 D1 800 HJJ R68 SAP Basis System: Perform rollback
2007 12 14 16:10:11 D0 800 HJJ AB1 SAP Basis System: > Short dump "071214 161011 SAPIDES HJJ " generated
Error 2007 12 14 16:10:11 D0 800 HJJ AB0 SAP Basis System: Run-time error "SAPSQL_ARRAY_INSERT_DUPREC " occurred
2007 12 14 16:10:11 D0 800 HJJ R68 SAP Basis System: Perform rollback
Error 2007 12 14 16:08:30 DP Q0G SAP Basis System: Request (type DIA) cannot be processed
Information 2007 12 14 16:08:30 D0 800 HJJ R47 SAP Basis System: Delete session 001 after error 004
2007 12 14 16:08:29 D0 800 HJJ R68 SAP Basis System: Perform rollback
Information 2007 12 14 16:08:29 D0 800 HJJ R2C SAP Basis System: Terminal 00020 in status DISC
2007 12 14 16:07:56 D1 800 HJJ AB1 SAP Basis System: > Short dump "071214 160756 SAPIDES HJJ " generated
Error 2007 12 14 16:07:56 D1 800 HJJ AB0 SAP Basis System: Run-time error "TIME_OUT " occurred
2007 12 14 16:07:55 D1 800 HJJ R68 SAP Basis System: Perform rollback
Error 2007 12 14 15:59:14 DP Q04 SAP Basis System: Connection to user 33 (HJJ ), terminal 20 (user24 ) lost
Error 2007 12 14 15:59:13 DP Q0I SAP Basis System: Operating system call recv failed (error no. 10054)
2007 12 14 15:56:39 D1 800 HJJ R64 SAP Basis System: > CPI-C function: CMINIT(SAP)
Warning 2007 12 14 15:56:39 D1 800 HJJ R49 SAP Basis System: Communication error, CPIC return code 020, SAP return code -01
2007 12 14 15:56:18 D1 800 HJJ R64 SAP Basis System: > CPI-C function: CMINIT(SAP)
Warning 2007 12 14 15:56:18 D1 800 HJJ R49 SAP Basis System: Communication error, CPIC return code 020, SAP return code -01
2007 12 14 15:55:51 D0 800 HJJ R64 SAP Basis System: > CPI-C function: CMINIT(SAP)
Warning 2007 12 14 15:55:51 D0 800 HJJ R49 SAP Basis System: Communication error, CPIC return code 020, SAP return code -01
2007 12 14 15:55:29 D1 800 HJJ R64 SAP Basis System: > CPI-C function: CMINIT(SAP)
Warning 2007 12 14 15:55:29 D1 800 HJJ R49 SAP Basis System: Communication error, CPIC return code 020, SAP return code -01
2007 12 14 15:55:08 D1 800 HJJ R64 SAP Basis System: > CPI-C function: CMINIT(SAP)
Warning 2007 12 14 15:55:08 D1 800 HJJ R49 SAP Basis System: Communication error, CPIC return code 020, SAP return code -01
2007 12 14 15:52:55 D0 800 HJJ R64 SAP Basis System: > CPI-C function: CMINIT(SAP)
Warning 2007 12 14 15:52:55 D0 800 HJJ R49 SAP Basis System: Communication error, CPIC return code 020, SAP return code -01
2007 12 14 15:52:34 D0 800 HJJ R64 SAP Basis System: > CPI-C function: CMINIT(SAP)
Warning 2007 12 14 15:52:34 D0 800 HJJ R49 SAP Basis System: Communication error, CPIC return code 020, SAP return code -01
2007 12 14 15:52:13 D0 800 HJJ R64 SAP Basis System: > CPI-C function: CMINIT(SAP)
Warning 2007 12 14 15:52:13 D0 800 HJJ R49 SAP Basis System: Communication error, CPIC return code 020, SAP return code -01
2007 12 14 15:51:52 D0 800 HJJ R64 SAP Basis System: > CPI-C function: CMINIT(SAP)
Warning 2007 12 14 15:51:52 D0 800 HJJ R49 SAP Basis System: Communication error, CPIC return code 020, SAP return code -01
2007 12 14 15:51:31 D0 800 HJJ R64 SAP Basis System: > CPI-C function: CMINIT(SAP)
Warning 2007 12 14 15:51:31 D0 800 HJJ R49 SAP Basis System: Communication error, CPIC return code 020, SAP return code -01
2007 12 14 15:51:10 D0 800 HJJ R64 SAP Basis System: > CPI-C function: CMINIT(SAP)
Warning 2007 12 14 15:51:10 D0 800 HJJ R49 SAP Basis System: Communication error, CPIC return code 020, SAP return code -01
2007 12 14 15:50:46 D1 800 HJJ R64 SAP Basis System: > CPI-C function: CMINIT(SAP)
Warning 2007 12 14 15:50:46 D1 800 HJJ R49 SAP Basis System: Communication error, CPIC return code 027, SAP return code 242
Error 2007 12 14 15:50:46 RD Q0I SAP Basis System: Operating system call SiPeekPendConn failed (error no. 45984)
Error 2007 12 14 15:50:24 RD Q0I SAP Basis System: Operating system call gethostbyaddr failed (error no. 0 )
2007 12 14 15:50:16 D0 0 SAPSYS GC4 Operation trace: >>> Profile name = C:\usr\sap\HIS\SYS\profile\HIS_DVEBMGS00_SAPIDES
Warning 2007 12 14 15:50:16 D0 0 SAPSYS GC3 Operation trace: The active profile was modified
Error 2007 12 14 15:49:21 B4 0 SAPSYS CP3 SAP Basis System: Character set '8300' does not appear in table 'TCPDB'
2007 12 14 15:49:21 B4 0 SAPSYS CPG SAP Basis System: Failed to Set Environment for Language M Code Page 8300 Locale CHT_TWN.950
Error 2007 12 14 15:49:21 B4 0 SAPSYS CP3 SAP Basis System: Character set '1610' does not appear in table 'TCPDB'
2007 12 14 15:49:21 B4 0 SAPSYS CPG SAP Basis System: Failed to Set Environment for Language T Code Page 1610 Locale Turkish_Turkey.28599
Error 2007 12 14 15:49:21 B4 0 SAPSYS CP3 SAP Basis System: Character set '8600' does not appear in table 'TCPDB'
2007 12 14 15:49:21 B4 0 SAPSYS CPG SAP Basis System: Failed to Set Environment for Language 2 Code Page 8600 Locale Thai_Thailand.874
Error 2007 12 14 15:49:21 B4 0 SAPSYS CP3 SAP Basis System: Character set '1401' does not appear in table 'TCPDB'
2007 12 14 15:49:21 B4 0 SAPSYS CPG SAP Basis System: Failed to Set Environment for Language Q Code Page 1401 Locale Slovak_Slovak.28592
Error 2007 12 14 15:49:21 B4 0 SAPSYS CP3 SAP Basis System: Character set '1500' does not appear in table 'TCPDB'
2007 12 14 15:49:21 B4 0 SAPSYS CPG SAP Basis System: Failed to Set Environment for Language R Code Page 1500 Locale Russian_Russia.28595
Error 2007 12 14 15:49:21 B4 0 SAPSYS CP3 SAP Basis System: Character set '1401' does not appear in table 'TCPDB'
2007 12 14 15:49:21 B4 0 SAPSYS CPG SAP Basis System: Failed to Set Environment for Language L Code Page 1401 Locale Polish_Poland.28592
Error 2007 12 14 15:49:21 B4 0 SAPSYS CP3 SAP Basis System: Character set '8500' does not appear in table 'TCPDB'
2007 12 14 15:49:21 B4 0 SAPSYS CPG SAP Basis System: Failed to Set Environment for Language 3 Code Page 8500 Locale Korean_Korea.949
Error 2007 12 14 15:49:21 B4 0 SAPSYS CP3 SAP Basis System: Character set '8000' does not appear in table 'TCPDB'
2007 12 14 15:49:21 B4 0 SAPSYS CPG SAP Basis System: Failed to Set Environment for Language J Code Page 8000 Locale Japanese_Japan.932
Information 2007 12 14 15:49:21 B4 0 SAPSYS E00 Operation trace: New System Log File Started with Number 4
Error 2007 12 14 15:49:21 B4 0 SAPSYS CP3 SAP Basis System: Character set '1401' does not appear in table 'TCPDB'
2007 12 14 15:49:21 B4 0 SAPSYS CPG SAP Basis System: Failed to Set Environment for Language C Code Page 1401 Locale Czech_Czech.28592
Information 2007 12 14 15:48:10 D0 0 SAPSYS A10 SAP Basis System: Initialization complete
Information 2007 12 14 15:48:02 D1 E10 SAP Basis System: Buffer RSCPCCC Generated with Length 6000000
2007 12 14 15:48:00 D0 AV6 Security: Initialization SCSA for Security Audit completed, number of selections 02
Information 2007 12 14 15:47:59 D0 BB0 SAP Basis System: Buffer CALE started with 500000 bytes
Information 2007 12 14 15:47:59 D0 BB0 SAP Basis System: Buffer OTR started with 4096k bytes
Information 2007 12 14 15:47:59 D0 BB0 SAP Basis System: Buffer CUA started with 3000k bytes
Information 2007 12 14 15:47:59 D0 BB0 SAP Basis System: Buffer ESM started with 4096k bytes
Information 2007 12 14 15:47:59 D0 BB0 SAP Basis System: Buffer EIBUF started with 4096k bytes
Information 2007 12 14 15:47:59 D0 BB0 SAP Basis System: Buffer TABLP started with 10240000 bytes
Information 2007 12 14 15:47:59 D0 BB0 SAP Basis System: Buffer TABL started with 30000128 bytes
InformationHi,
if you are wokrng on windows go to RUN-->services.msc
and check out if the services of sap are runnning (SAPOSCOLL,SAPSID_NR)
and provide the trace files from the work directory
regards
Abdul -
Short dump with the transaction CJ02
Hello, this is my first thread in the forum. I hope to solve my problem.
It is necesary to say you that my english is very poor, is not so good. Sorry for that.
When i use the transaction CJ02 to finish or close a project, appears an error when i save it. The steps are the followings:
1- Run the transaction CJ02 with a WBS element
2- Mark the line of the WBS element
3- Select then button Settlement rule
4- Fill 4 items in the next screen to distribution rules (the % is 100)
5- Back with green arrow
6- Fill the field Cost Center Req
7- Save
After a few seconds appears the dump:
<b>ABAP runtime errors MESSAGE_TYPE_X
Occurred on 20.11.2006 at 11:07:09
>> Short dump has not been completely stored. It is too big.
The current application triggered a termination with a short dump.
Error analysis
Short text of error message:
Nested call of PERFORM ON COMMIT:
Long text of error message:
Diagnosis
During processing of a routine called using PERFORM ... ON COMMIT,
the system attempted to call PERFORM ... ON COMMIT again. Nesting
of this is not allowed.
System Response
Procedure
The program indicated after "Caller:" must be changed. This is the
program that calls the routine indicated after "Form:" during
COMMIT processing. This routine is part of the program indicated
after
"Program:".
Procedure for System Administration
Technical information about the message:
Message classe...... 00
Number.............. 081
Variable 1.......... " "
Variable 2.......... " "
Variable 3.......... " "
Variable 4.......... " "
How to correct the error
If the error is in one of your own ABAP programs or an SAP program that
you have modified, try to correct it.
If the error occurred in a non-modified SAP program, you may be
able to find a solution in the SAP note system.
If you have access to the note system yourself, use the following
search criteria:
"MESSAGE_TYPE_X"
"SAPMSSY0 " or "SAPMSSY0 "
"%_ORDER_FORM_FOR_ROLLBACK"</b>
There are several notes that apparently solve the problem with support packages that are applied in our system (for example 397011 or 614553). Inthis case our system is updated.
Can you help me please.
Thanks
Gabriel.-Hi
Are you really sure https://websmp101.sap-ag.de/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=397011&_NLANG=E
is applied correctly ?
Try downloading with snote and see if it gets marked 'not relevant',
( are you on release 4.6 ? )
Given the nature of the problem ( and the fact that this issue is known ) , the best seems log an OSS support request
rgds
Dirk -
Abap error when user fi asset using tcode KO88
hai gurus,
when the user fi_asset team want to use the transaction the system give and error.
For gurus information, we are facing the number ranges issue. when document type AA that using number ranges from 100006000 - 100006999 have been hit to maximum value in year 2007
so the at the time is we create a another number ranges in documnet type AA using number ranges form 8000000000 - 8999999999 that for year 2007 untill the future
but now when the user want to use this transaction the system have issue the problem.
when the user run the test run mode is no detect any problem but when user make actual run the system give abap error like this below.
ABAP runtime errors MESSAGE_TYPE_X
Occurred on 22.02.2008 at 09:58:49
>> Short dump has not been completely stored. It is too big.
The current application triggered a termination with a short dump.
What happened?
The current application program detected a situation which really
should not occur. Therefore, a termination with a short dump was
triggered on purpose by the key word MESSAGE (type X).
What can you do?
Note the actions and input that caused the error.
Inform your SAP system administrator.
You can print out this message by choosing "Print". Transaction ST22
allows you to display and manage termination messages, including keeping
them beyond their normal deletion date.
Error analysis
Short text of error message:
Document number 1000 100060000 2007 was already assigned
Long text of error message:
Diagnosis
Document number 100060000 in company code 1000 and fiscal year 2007
has already been assigned.
System Response
Termination of processing.
Procedure
Check document number range 01 in company code 1000 and fiscal year
2007 and correct the number range status if necessary.
Technical information about the message:
Message classe...... "F5 "
Number.............. 152
Variable 1.......... "1000 "
Variable 2.......... "100060000 "
Variable 3.......... "2007 "
Variable 4.......... "01 "Hello,
If you are facing the error during KO88, there could be a problem with settlement document number range also.
During settlement, a settlement document is created and also related FI, CO, PA documments as applicable.
Please go to t code SNUM, check the number range for CO settlement object:CO_ABRECHN.
Let me know if it solves your problem.
Sourabh -
Deletion of component in IW32 - DUMP ERROR due to purchase requisition ??
Hello,
I created a PM order in IW31 with a component that is linked to a purchase requisition. The P.R. is not released. I want to delete this component in IW32 but when I try to, I get the following error message: Is it a functional issue or a basis issue ?
Runtime errors MESSAGE_TYPE_X
Occurred on 09.12.2009 at 10:19:29
>> Short dump has not been completely stored. It is too big.
The current application triggered a termination with a short dump.that is what you have to analyze.
Goto ST22 for this. read the dump content. the first 8 pages will give you the most info.
it can be caused by program error of SAP, then you should search OSS to find a solution.
The dump gives you information about the keywords you should use for the search. -
Please any one give me solution for this issue.
Mail: [email protected]
In BWP, we now get an abap dump when using tcode rsa11.... this is after
transport of new ods object zrebudget. The BWD and BWT clients are ok,
so I don't know why BWP is bad.
Thanks & Regards,
Muddu Reddy.Hi,
Now it gives short dump in my system also.if i enter rsa1 and rsa11 also it give s short dump.
Runtime Error MESSAGE_TYPE_X
Occurred on 02/06/2008 at 03:31:16
What happened?
The current application program detected a situation which really
should not occur. Therefore, a termination with a short dump was
triggered on purpose by the key word MESSAGE (type X).
What can you do?
Print out the error message (using the "Print" function)
and make a note of the actions and input that caused the
error.
To resolve the problem, contact your SAP system administrator.
You can use transaction ST22 (ABAP Dump Analysis) to view and administer
termination messages, especially those beyond their normal deletion
date.
is especially useful if you want to keep a particular message.
Error analysis
Short text of error message:
LOCAL_ENTRY_NOT_FOUND
Technical information about the message:
Message classe...... "R7"
it gives thiss short dump.....please let me now the solution -
Cutover strategy for Cash Management
Hi Gurus,
Please tell me about the cutover strategy for Cash Management??
We are implementing Cash Management in mid year, so how can we take the data in effect which is already posted in the system??
Please revert asap.
Thank Youdear Simmi,
for delta queue check this
https://websmp104.sap-ag.de/~sapidb/011000358700001584392004#17
I intend to copy the source system, i.e. make a client copy. What will happen with may delta? Should I initialize again after that?
Before you copy a source client or source system, make sure that your deltas have been fetched from the DeltaQueue into SAP NetWeaver BI and that no delta is pending. After the client copy, an inconsistency might occur between SAP NetWeaver BI delta tables and the OLTP delta tables as described in Note 405943. After the client copy, Table ROOSPRMSC will probably be empty in the OLTP since this table is client-independent. After the system copy, the table will contain the entries with the old logical system name which are no longer useful for further delta loading from the new logical system. The delta must be initialized in any case since delta depends on both the SAP NetWeaver BI system and the source system. Even if no dump 'MESSAGE_TYPE_X' occurs in SAP NetWeaver BI when editing or creating an InfoPackage, you should expect that the delta has to be initialized after the copy.
Maybe you are looking for
-
Easylink advisor link or software needed please help me
i need the software for the linksys easylink advisor for the router wrt54gs version 6. i have 2 computers at my house and the one that had all my router information officially broke ( i saw it coming it was 10 years old and i did not take care of it
-
Macbook Pro will not boot up / circle with line in it
Mid 2012 MacBook Pro bought brand new OS X Yosemite Core i7 16Gb memory (upgraded shortly purchase) 500Gb SATA About a month ago my laptop started running really slow then locked up, I had to hard power down and every since it will not boot up, all I
-
Trouble with newer versions of Firefox on Windows XP
Long time Firefox user but started having problems a few updates ago. Uninstalled 8.0 and reinstalled newest version. Have not added any plugins/add-ons with install yet list below shows many (some unrecognizable (did not save any old settings with u
-
Offcycle - Default value Paymnet method
Hi All, Requirement : to default all ofcycle as cash pay (/557). For this we have done config chnage in table V_T520CB , assigned one ofcy reason to "check" . but still the chnages only reflecting / defaulting /557 only in PUOC_99, but not in PC00_M9
-
Cffileupload_swf.js parameters are all wrong
I am running ColdFusion on Windows. The version information is shown below. When implementing cffileupload the attributes specified get mismanaged when CF invokes cffileupload_swf.js If I specify extensionfilter values, that ends up getting prefix