" The role of the update work process is very important since it is responsible for recording the changes in the database. The process performs its functions when the ABAP applications are programmed with the statements in the UPDATE TASK. This type of updating is asynchronously performed, ie. The programs leave update records in a queue to be processed and then continue to the update process. Normally, it runs without any intervention from the SAP R/3 management, still R/3 includes utilities to monitor check and perform management operations on the updation processes. In case any updating error takes place, the system places a message to the user regarding the error and an alert is triggered in the CCMS monitor. For the update functions go to Administration menu bar option --> Monitor option ---> Update option. An initial update screen showing various functions appears. The initial update screen is used to display the system update records with error status or the records which have not yet been processed, activate and deactivate the updating in the whole SAP system. It is also useful to display the update statistics, to display the data on the erroneous update records and reprocess them, either in real or in test mode and to send waiting update records for processing after a deactivation/activations of the updating and delete update records. Many work processes of the type R/3 system update the database. A database interface is included by the dialog and background work processes, which can directly update the database. However, the update work processes ca also be used for updating the physical database in asynchronous way. If it is asynchronous updating, according to which the transactions are programmed in the ABAP business applications, then in the database commit phase, the transactions pass the update records to the update work processes."
"The flow of a program is determined by a sequence of screens in a dialog transaction. The screens that are called within a transaction, must belong to a single ABAP program, usually a module pool (Type M). You have to use the transaction maintenance transaction (SE93) to create a dialog transaction. Once you have entered a transaction code and a short description, chose transaction type program and screen. Then enter data on the next screen as required. The transaction code in a dialog program must be linked to the number of its initial screen. Finally enter this number in the screen number field."
Tuesday, July 29, 2008
SAP Retail Transaction Codes: Subsequent Settlement
SAP for Retail is an end-to-end set of solutions that supports Demand-Management, Merchandise Management and Planning, Store Operations, and Base Finance and HR Functions.
Radio Frequency Identification Devices are responsible for electronically capturing the data related to Materials. Once the data is captured, it is transmitted via Radio waves to the SAP server. The main use of RFID devices is in Warehouses where the data is physically moved from one location to another. It is very convenient for the warehouse personnel to make use of RFID so that all the material movement is captured automatically and the information is transferred to the SAP server.
SAP Auto-ID Infrastructure is the component in SAP Netweaver that provides gateway to the RFID Data. SAp Auto-ID Infrastructure can be used to integrate the following devices.
RFID readers and printers Bluetooth devices Embedded systems Bar-code devices
SAP has extended its power by introducing ADOBE Forms. Interactive Forms based on Adobe software bridges the paper-to-digital divide by helping organizations create Adobe Portable Document Format (PDF) forms that have the same high-quality appearance and easy accessibility of familiar paper documents. By using information resident in SAP software, the Interactive Forms solution lets IT departments replace inefficient paper-based processes; include customers, partners, and employees in electronic processes; and extend the reach of enterprise applications to a much broader set of users inside and outside the firewall. Because the Interactive Forms solution harnesses the power of PDF and eXtensible Markup Language (XML), it helps IT departments streamline form processes and capture data more accurately. First, IT departments can easily design sophisticated forms that look like the pieces of paper they replace. Then, users can fill out forms with the ubiquitous Adobe Reader® software while online or offline—without buying additional software. And because PDF forms are intuitive and easy to fill out, IT departments eliminate time-consuming, expensive rekeying of data when users submit forms back to SAP systems in the enterprise.
To extract SAP Plant and Storage Location Data the following Function Module can be used
SAP ABAP Function Module to extract PLANT and STORAGE Location Data.
ITOB_CHECK_PLANT_STORAGE
_______________________________________________
Important SAP MASTER Tables associated with this Function Module are as follows.
TVKO SAP Sales organization TVTW SAP Distribution channel TVST SAP Shipping point/receiving point LFA1 SAP Vendor's account number KNA1 SAP Account number of customer T001W SAP Plant TSPA SAP Division
Import Parameters for the above mentioned Function Module are as follows
T001L-LGORT Storage location T001L-WERKS Plant SY-BINPT Batch input, program running under batch input (Dialog Mode) SY-BINPT Batch input, program running under batch input (Dialog Cursor) DD03D-FIELDNAME Field name SY-STEPL Screens, current table line index SY-BINPT Batch input, program running under batch input (Initial Message Data) SY-MSGTY Messages, message type
Plant, Storage location, Description of storage location, Division, Negative stocks allowed in storage location, Freezing book inventory bal., allowed in stor. loc., Storage location MRP indicator, Storage location authorization for goods movements active, Storage location is allocated to resource (storage resource), Handling unit requirement, Partner storage location of the handling unit, Sales organization, Distribution channel, Shipping point/receiving point, Vendor's account number, Account number of customer.
Always specify your conditions in the Where-clause instead of checking
them yourself with check statements. The database system can then use an index
(if possible) and the network load is considerably less.
Always use Pretty Printer and Extended Program Check before releasing the code.
Do not leave unused code in the program. Comment the code thoroughly. Align the comments and the Code. Follow the SAP Standards and SAP Best Practices guidelines. It’s a good practice to take a dump of the code on your local drive.
