Вы находитесь на странице: 1из 7

KONV KONP LIKP LIPS VBAK VBAP VBBE VBEH VBEP VBFA VBLB VBLK VBPA VBRK VBRP

VBUK VBUP VEKP VEPO VEPVG

Conditions for Transaction Data Conditions for Items Delivery Header Data Delivery: Item data Sales Document: Header Data Sales Document: Item Data Sales Requirements: Individual Records Schedule line history Sales Document: Schedule Line Data Sales Document Flow Sales document: Release order data SD Document: Delivery Note Header Sales Document: Partner Billing: Header Data Billing: Item Data Sales Document: Header Status and Administrative Data Sales Document: Item Status Handling Unit - Header Table Packing: Handling Unit Item (Contents) Delivery Due Index

MM
EINA EINE MAKT MARA MARC MARD MAST MBEW MKPF MSEG MVER MVKE RKPF T023 T024 T156 T157H MOFF Purchasing Info Record- General Data Purchasing Info Record- Purchasing Organization Data Material Descriptions General Material Data Plant Data for Material Storage Location Data for Material Material to BOM Link Material Valuation Header- Material Document Document Segment- Material Material Consumption Sales Data for materials Document Header- Reservation Mat. groups Purchasing Groups Movement Type Help Texts for Movement Types Lists what views have not been created

mm-purchasing
A501 EBAN EBKN EKAB EKBE EKET EKKN EKKO EKPO IKPF ISEG LFA1 Plant/Material Purchase Requisition Purchase Requisition Account Assignment Release Documentation History per Purchasing Document Scheduling Agreement Schedule Lines Account Assignment in Purchasing Document Purchasing Document Header Purchasing Document Item Header- Physical Inventory Document Physical Inventory Document Items Vendor Master (General section)

LFB1 NRIV RESB T161T

Vendor Master (Company Code) Number range intervals Reservation/dependent requirements Texts for Purchasing Document Types

Production Planning
MAST STKO STPO MAPL PLKO PLSO PLPO AFKO AFPO Material BOM BOM Header BOM Positions (detail) Assignment fo Task Lists to Materials Routing Group Header Routing Group Sequence Routing Group Operations Production Order Header Production Order Position (details) search_sap_menu - Finds the menu path to a transaction - Can either type in TX code in the search criteria or a description- ie. 1st try SE38 and then ABAP.... the returned result is 'bottom to top'.

EDI Specific Transactions VOE1 Translation between EDI categories and SD item categories VOE2 Table EDSC view. Customer link to sales area detail VOE3 Table view EDPVW. Add partner types that will be transferred to the IDoc VOE4 Table view EDPAR. Link external partner number with our internal number WEDI EDI Administrator Menu BALE Idoc Administration Scheduling agreements OVA9 Create entries for each sold-to customer for which you will receive EDI schedule

releases. At implementation, the only field that needs to be maintained is "Check PO number," which causes SAP to make sure that the PO number sent on the release matches the PO number on the schedule agreement. This transaction updates table T663A. SAP will not post an EDI schedule release, if this record is missing. OVAI Create entries for each Vendor / Partner description combination. (Vendors must match sold-to Acct. at Cust., and Partner descriptions must match ship-to Partner descriptions.) This transaction updates table T661W. SAP uses this table to determine the schedule agreement soldto partner. OVAJ If you would like SAP to post schedule requirements using discrete dates only, instead of weekly and/or monthly buckets, you can indicate the days of the week that you deliver to this customer. SAP will divide the customer's quantity for a week or month evenly into the days of the week specified by the distribution function code. This code must be sent in the DELINS IDoc in field E1EDP16-ETVTF. IDoc lists according to content. View IDocs via specific IDoc number or business application detail contained within the contents of a segment. WE05 View IDocs WE19 EDI test tool. Use to test inbound Function module changes. WE20 Partner profile configuration. Add partner detail together with inbound and outbound relationships. We also incorporate message control on the outbound IDocs. Utilize the organizational units to trap functional errors for further processing WE30 Create IDoc extension type WE31 WE57 WE60 WE82 Segment create Assign function module to logical message and IDoc type IDoc type documentation tool Link Release detail to Extension IDoc Type

IDoc Transactions WE09 / WE02

BD55 Conversion rule user exit. Link conversion rule user exit to the different system \ partner combinations

BALM ALE Master Data Distribution Output determination 856 - ASN V/36 Maintain output determination for deliveries (Output determination procedures). V10000
(Header output) has condition type LAVA (usually with requirement 1 NB: Use V/84 V7ALLE SHAD for grouped ASNs. I.e. Group deliveries into shipments VV21,VV22,VV23 Create output condition records for shipping. LAVA WE (Partner function) - We must add each new partner with VV21 VL71 Reissue output for deliveries

BD87 Reprocess IDocs in error or waiting for action. (Both inbound and outbound in 4.6. Use BD88 in prior versions) BALA ALE Application Distribution

810 - Invoice V/54 Maintain access sequence for billing documents VV31,VV32,VV33 Create condition records for billing documents. (RD00 RE Billing
party)

VF31 Reissue output for billing documents 855 Order Response V/30 Sales document output types (BA00) V/48, V/32, V/43 Maintain access sequence for sales documents VV11,VV12,VV13 Create condition records for sales documents. (BA00 SP Sold to
party)

Requirements coding V/27 Create code to check requirements for output control. Used to check ZBA0 against BA00
output.

Sales & Distribution Sales order / Quote / Sched Agreement / Contract VA02 Sales order change VA05 List of sales orders VA22 Quotation change VA32 Scheduling agreement change VA42 Contract change Billing VF02 Change billing document VF11 Cancel Billing document VF04 Billing due list FBL5N Display Customer invoices by line FBL1N Display Vendor invoices by line Delivery VL02N Change delivery document VL04 Delivery due list VKM5 List of deliveries VL06G List of outbound deliveries for goods issue VL06P List of outbound deliveries for picking VL09 Cancel goods issue VT02N Change shipment VT70 Output for shipments General VKM3, VKM4 List of sales documents VKM1 List of blocked SD documents VD52 Material Determination Workflow SWEAD Event queue administration SWE2 Event type linkages

SWE3 PPOME SWE5 SWUD General

Event linkages Organizational Unit Maintenance Consistency Checks for Event Linkages Workflow Diagnostic Tool

The following section provides detail on other useful SAP areas.


Create delivery via transfer orders

Once the order is saved proceed through the following steps. The process assumes the item has values in the warehouse bin.

VL04 LT03 Delivery due list. Run the delivery due with your order number to create the delivery Create Transfer Order. EG. Warehouse: 101 and enter. Picking background. Save

The Transfer order should now be saved. It now needs to be confirmed.


In LT03 go to menu option Transfer Order -> Confirm Transfer Order Enter Save

The transfer order is now confirmed.

VL02N Delivery change. EG: Edit the delivery to do the following Pack External customer material number = COO. External delivery number Waybill number. BOL Transport tag. Carrier Header partner SP (E.G. FXP). Tracking number = Packing Unit

Purchase Orders ME22N POChange ME57 Create POfrom purchase requisition ATP CO09 Availability overview Goods Movement MIGO Post goods receipt MB51 Material document list MB01 Goods Movement Other MD04 Material Requirements. Shows material requirements and releases against materials SE38 ABAP Editor. Used to modify ABAP programs SM01 Transaction list. Lock transactions in the system. Also a good tool to see what
transactions are available SHDB Transaction recorder (BDC) CMOD User exit \ project tool. Coordinates your changes into projects for the purpose of activating all user exits for a particular project. A user exit needs to be modified before it will work SE16 Table contents display SOST SU53 SQVI ST22 ST01 ST11 ST05 SM21 ST22 View mails sent externally from SAP Check authorization object Table Quickviewer Used to created quick client dependent reports ABAP Dump Analysis System trace Display developer trace SQL Trace System log Display short dumps

SM12

Display locked entries

Programs List of ABAP Reports Idoc RBDAPP01 Post inbound Idocs to application documents RBDAGAI2 Re-processing of IDocs after ALE input error RBDAGAIE Reprocessing of edited IDocs RBDMANIN Start error handling for non-posted Idocs RSEINB00 Idoc inbound processing by file RSEOUT00 Process outbound IDocs General RV80HGEN Report 'RV80HGEN' for including customer-specific routines in the SAP standard
source code is not included automatically as an XPRA in the object list of the transport request. See OSS note 0385067. This report needs to be run in target clients once you have implemented a custom requirements definition. RSWUWFML Report that interrogates the Workflow inbox, based on certain selections, and then forwards a notification to the respective users that they have email waiting in the SAP system. The auto-forwarding assignment of an email address to a user can be accomplished by the administrator and tx: SO36 or by the user themselves using tx: SO13. Use tx: SOST to view email status sent from SAP. RHSOBJCH Corrects the following error in workflow customizing: Transport object PDST Information Table SOBJ is consistent as regards key tables ***Error*** Table HRP1600 Not an entry in table SOBJ Information Table SOBJ is consistent as regards PAD tables See note 134311 (point 2). Note 60801 also recommends the same steps regarding RHSOBJCH. RSPO0075 Run report RSPO0075 to activate access method M for device types.

List of ABAP Reports Idoc RBDAPP01 Post inbound Idocs to application documents RBDAGAI2 Re-processing of IDocs after ALE input error RBDAGAIE Reprocessing of edited IDocs RBDMANIN Start error handling for non-posted Idocs RSEINB00 Idoc inbound processing by file RSEOUT00 Process outbound IDocs General RV80HGEN Report 'RV80HGEN' for including customer-specific routines in the SAP standard
source code is not included automatically as an XPRA in the object list of the transport request. See OSS note 0385067. This report needs to be run in target clients once you have implemented a custom requirements definition. RSWUWFML Report that interrogates the Workflow inbox, based on certain selections, and then forwards a notification to the respective users that they have email waiting in the SAP system. The auto-forwarding assignment of an email address to a user can be accomplished by the administrator and tx: SO36 or by the user themselves using tx: SO13. Use tx: SOST to view email status sent from SAP. RHSOBJCH Corrects the following error in workflow customizing: Transport object PDST Information Table SOBJ is consistent as regards key tables ***Error*** Table HRP1600 Not an entry in table SOBJ Information Table SOBJ is consistent as regards PAD tables See note 134311 (point 2). Note 60801 also recommends the same steps regarding RHSOBJCH. RSPO0075 Run report RSPO0075 to activate access method M for device types.

ABCDE APPLI

IF SY-BATCH EQ SPACE. WRITE: / 'Report was started on-line'. BATCH WRITE: / 'Using variant:', SY-SLSET. ELSE. ABAP_DOCU_DOWNLOAD WRITE: / 'Report was started in background'. Download ABAP documentation in HTML format. ENDIF.

Constant: Alphabet (A,B,C,...) SAP applications Background active (X)

BATZD Background SUBMIT: Daily BATZM Background SUBMIT: Monthly BATZO Background APPL_LOG_DELETE SUBMIT: Once With this function module you delete logs in the database according to specified selection BATZS Background SUBMIT: Immediately conditions BATZW Background SUBMIT: Weekly Batch input active (X) This field indicates if the transaction was called in a Batch Input session or by an online APPL_LOG_DISPLAY user. To test it, a batch input session must be created. From Release 3.1g the next procedure in be database. With this function module you can analyze logscan the used.
o Create a report which displays this system field o Create a Transaction code for this report o Use transaction SHDB to record a the previous transaction o Press the APPL_LOG_DISPLAY_INTERN Overview button and choose the 'generate program' function. Running the previously generated program it will create a Batch Input With this function moduleoyou can analyze logs in local memory, e.g. when you have only

BINPT

collected log records at runtime and do not want to writeprocess the created Batch Input in o Now call transaction SM35 and to the database.
foreground. It should display an 'X' for system field SY-BINPT.

session

BREP4 Background SUBMIT: Root name of request report BSPLD Background SUBMIT: List output to spool APPL_LOG_INIT CALL checks whether This function module mode active (X)the specified object or sub-object exists and deletes all existing associated data in local memory. This field indicates if the transaction was called from another transaction. CALLD
o o o
Create a report which displays this system field Create a Transaction code for this report Create a new report containing the next ABAP command: CALL TRANSACTION tcode. Where tcode is the Transaction code you created. When you readyou run this report,theshould display an 'X' for system field SYthe log data in it database for an object or sub-object CALLD.

APPL_LOG_READ_DB With this function module according to specified selection conditions. CALLR Print: ID for print dialog function

CCURS Rate specification/result field (CURRENCY CONVERT) CCURT Table rate from currency conversion APPL_LOG_READ_INTERN currency conversion CDATE Date of rate from With this function module you during list creation Current column read all log data whose log class has at least the specified value, COLNO WRITE: SY-COLNO, ',', SY-LINNO, 'Cursor from local memory, for the specified object or sub-object. position (column, row).'. Current page number CPAGE
WRITE: / 'SY-CPAGE:', SY-CPAGE LEFT-JUSTIFIED.

Runtime: Main program CPROG WRITE: /5 APPL_LOG_SET_OBJECT 'Main program:' RIGHT-JUSTIFIED, 40 SY-CPROG. CTABL Exchange rate table from currency conversion With this function module, you create a new object or sub-object for writing in local memory. With a flag you can control whether the APPL_LOG_WRITE_... messages are written in local CTYPE Exchange rate type 'M','B','G' from CURRENCY CONVERSION memory or are Cursor position (column) output on the screen. CUCOL
WRITE: / 'SY-CUCOL:', SY-CUCOL LEFT-JUSTIFIED.

CUROW

Cursor position (line)

WRITE: / 'SY-CUROW:', SY-CUROW LEFT-JUSTIFIED.

APPL_LOG_WRITE_DB Flag: Data received With this function module you write all data for the specified object or sub-object in local memory In transaction programming this field indicates the change of data on the to the database. If the log for the object or sub-object in question is new, the log number is screen. In the PBO part you may set default values of the input fields of the DATAR dynpro. In the PAI part you can check if they were changed. If SYDATAR is set, then the user has modified or entered new data on the screen. DATLO Local date for user

DATUM DATUT DAYST DBCNT DBNAM DBSYS DCSYS DSNAM DYNGR DYNNR FDAYW

System: Date Global date related to UTC (GMT) Summertime active ? ('daylight saving time') Number of elements in edited dataset with DB operations
WRITE: /12 'Number of selected records:', SY-DBCNT CENTERED.

Logical database for ABAP/4 program System: Database system System: Dialog system Runtime: Name of dataset for spool output Screen group of current screen Number of current screen Factory calendar weekday Location of a string

FDPOS

SEARCH T FOR 're'. READ TABLE T INDEX SY-TABIX. WRITE: / SY-TABIX, T-FIELD. SKIP. WRITE: /9 'At the example of sy-tabix, Row', (3) SY-TABIX, ',' , 'keyword ''re'' found at off-set position:', (3) SY-FDPOS.

FMKEY HOST INDEX LANGU LDBPG

Current function code menu Host Number of loop passes


DO 5 TIMES. WRITE: SY-INDEX. ENDDO.

SAP logon language key Program: ABAP/4 database program for SY-DBNAM Number of current list line
AT LINE-SELECTION. DETAIL. * SY-LSIND is the index of the current list WRITE: / 'SY-LSIND:', SY-LSIND LEFT-JUSTIFIED. * SY-LISTI is the index of the previous list WRITE: / 'SY-LISTI:', SY-LISTI LEFT-JUSTIFIED. * SY-LILLI is the number of the selected line in the absolute list WRITE: / 'SY-LILLI:', SY-LILLI LEFT-JUSTIFIED.

LILLI

LINCT LINNO LINSZ LISEL LISTI LOCDB LOCOP LOOPC LSIND LSTAT MACDB MACOL MANDT MARKY MAROW MODNO MSGID

Number of list lines


WRITE: / SY-LINCT, 'line and', (3) SY-LINSZ, 'column is a page'.

Current line for list creation Line size of list

WRITE: SY-COLNO, ',', SY-LINNO, 'Cursor position (column, row).'. WRITE: SY-COLNO, ',', SY-LINNO, 'Cursor position (column, row).'.

Interact.: Selected line

* contents of the selected line WRITE: / 'SY-LISEL:', SY-LISEL. * SY-LISTI is the index of the previous list WRITE: / 'SY-LISTI:', SY-LISTI LEFT-JUSTIFIED.

Number of current list line

Local database exists Local database operation Number of LOOP lines at screen step loop Number of secondary list

* SY-LSIND is the index of the current list WRITE: / 'SY-LSIND:', SY-LSIND LEFT-JUSTIFIED.

Interact.: Status information for each list level Program: Name of file for matchcode access Number of columns from SET MARGIN Client number from SAP logon Current line character for MARK No. of lines from SET MARGIN statement Number of alternative modi Message ID

Вам также может понравиться