Josephreddy

http://scn.sap.com/docs/DOC-64578

End Routine Parameters End Routine Parameters Importing ● REQUEST: Request ID ● DATAPAKID: Number of current data package Exporting ● MONITOR: Table for user-defined monitoring. This table is filled using row structure MONITOR_REC (the record number of the processed record is inserted automatically from the framework). Changing ● RESULT_PACKAGE: Contains all data that has been processed by the transformation. Raising ● CX_RSROUT_ABORT: If a raise exception type cx rsrout_abort is triggered in the routine, the system terminates the entire loading process. The request is highlighted in the extraction monitor as Terminated. The system stops processing the current data package. This can be useful with serious errors. By default, only fields that have a rule in the transformation are transferred from the end routine. Choose Change Update Behavior of End Routine to set the All Target Fields (Independent of Active Rules) indicator. As a result, fields that are only filled in the end routine a...

Frequently Asked Questions around SAP BW DeltaQueue (RSA7) What does the number in the 'Total' column in Transaction RSA7 mean? 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. What is a LUW in the delta queue? 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. 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? The number on the overview screen corresponds to the total of...

For IT enabled companies, in real time business scenario audit teams are focused on user access and authorization controls. The user access and authorization management is manual and it is error prone. Approval from manger for new access or change access credentials takes time and monitoring is difficult.Emergency or unexpected access maintenance is difficult. Giving unauthorized access is a violation/Risk, which causes to make fraud. Detection of these violations for user/roles is difficult. To make IT systems with audit compliance standards. SAP has given solution with the product GRC (Governance Risks & Compliance). SAP GRC solution help companies comply with Sarbanes-Oxely Act and other audit mandates by enabling organizations to rapidly identify and remove the access and authorization risk from IT systems and embed preventive controls into business processes to stop future Segregation of Duties (SoD) violations from occurring. So with the GRC, IT systems access a...