abap_4 programming.pdf

4/8/2014 ABAP/4 Programming

http://abap4programming.blogspot.in/ 1/13

S U N D A Y , J U N E 2 2 , 2 0 0 8

BAPI For Goods Movement

BAPI FOR GOODS REECIPT FOR FOC MATERIAL

Bapi example for goods movement 511

We have a requirement to make a z-transaction to receive material

on free of goods .technically FOC material has 511 movement in t-

mb1c , FOC material comes without any reference to purchase order

but against a vendor code..

There were two technical solution one was to make BDC and another

was to find a suitable BAPI for goods receipt.

BAPIs are always preferred as they have standard coding checks while

posting the document .Also BAPIs have a test run environment which

checks for any kind of error before posting .To sum up we found BAPI

for FOC BAPI_GOODSMVT_CREATE .

T-CODE BAPI MATERIAL MANAGEMENT INVENTORY MANAGEMENT

GOODS RECEIPT CREATE FROM DATA SEE THE F.M.

In this document I am only considering only that aspects(technical

fields and implementations) of BAPI which I used as per my

requirement. In my case I have a gate entry before Goods receipt for

FOC , based on Gate entry number number we have to make BAPI.

Lets talk about the structure of BAPI: -

1. Goods movement header: This structure contains the header data

of the material document that is to be created. PSTNG_DATE : Date

which is used when entering the document in Financial Accounting or

Controlling. Value = sy-datum. DOC_DATE: The document date is the

date on which the original document was issued. Value = Gate entry

bill date. REF_DOC_NO: The reference document number can contain

the document number of the customer/vendor. However it may

contain a different value. Value = bill no of vendor as on gate entry.

BILL_OF_LADING: this field doesnt appear in t-mb1c but while

posting data this filed is capture in mkpf , so we decided to pass gate

entry number to this field so as to make record that goods receipt for

this gate entry has been made. HEADER_TXT: Manually input by the

user.

2. Goods Movement Code: This parameter transfers the new key

assignment of the GM_CODE to the relevant transactions in Inventory

Management. Assign code to transaction for BAPI goods movement.

Indicates the assignment of the code for the R/3 transaktionfor BAPIs

About Me

Vikram Bajaj

SAP-ABAP Technical Consultant

View my complete profile

Blog Archive

2008 (5)

June (1)

BAPI For Goods Movement

May (4)

Share 0 More Next Blog Create Blog Sign In

ABAP/4 ProgrammingCreated By Vikram Bajaj SAP ABAP/4 Programmer and SD Consultant



for goods movements.

Dependencies:Using this method, the system does not support goods

movements that are initiated by other application components. These

include:

Goods issue for delivery

Completion confirmation in production

Usage decision in QM

GM_CODE: The following sample scenarios demonstrate which fields

have to be filled for which business transactions/events (code).

There are the following types of transactions/events:

GM_Code 01: Goods receipt for purchase order

GM_Code 02: Goods receipt for production order

GM_Code 03: Goods issue

GM_Code 04: Transfer posting

GM_Code 05: Other goods receipts

GM_Code 06: Reversal of goods movements

GM_Code 07: Subsequent adjustment to a subcontract order

In our case GM_CODE = 05

3. TESTRUN = SPACE (FOR LIVE POSTING) / X FOR TEST CASE FOR

CHECKING ANY ERROR BEFORE POSTING.

4. Goods movement Item:

MATERIAL: From Gate Entry Number , multiple records of material

PLANT: input value STGE_LOC: input . MOVE_TYPE = '511'.

VENDOR = LIFNR_1. "lifnr in format 000002502

ITEM_TEXT = input

ENTRY_QNT = equals gate entry material quantity but in changed

mode for goods receipt.

ENTRY_UOM = MARA-MEINS

5 .GOODS MOVEMENT HEADER : This structure transfers the fields

that are filled to the initiator when the material document was

successfully posted.

MAT_DOC : Number of Material Document DOC_YEAR: Material

Document Year

6 .RETURN: This table contains the return codes from the method

call.

Default : There are numerous error messages, which cannot be

explained in detail here. If errors occured during this method, the

"Return" table is filled. Note that errors at header level are

characterized by an item number =0. If the method was carried out

without errors occuring, the "Return" table is reset to empty.

MOVE DATA OF RETURN INTO ITAB_RETUNR AND WRITE TO LIST.

NOTE: WHEN BAPI IS SUCCESSFUL WE MUST USE COMMIT

WORK*******************SAMPLE CODE***********************

GOODSMVT_HEADER_H-PSTNG_DATE = SY-DATUM.

GOODSMVT_HEADER_H-DOC_DATE = BLDAT.

GOODSMVT_HEADER_H-REF_DOC_NO = LFBNR .

GOODSMVT_HEADER_H-GR_GI_SLIP_NO = MBLNR.

GOODSMVT_HEADER_H-BILL_OF_LADING = MBLNR.

GOODSMVT_HEADER_H-HEADER_TXT = HEADER_TXT.

GOODSMVT_ITEM_I-PLANT = PLANT.

GOODSMVT_ITEM_I-STGE_LOC = STGE_LOC.

GOODSMVT_ITEM_I-MOVE_TYPE = '511'.



Posted by Vikram Bajaj at 9:15 PM

GOODSMVT_ITEM_I-VENDOR = LIFNR_1. "lifnr in format 000002502

LOOP AT ITAB.

GOODSMVT_ITEM_I-MATERIAL = ITAB-MATNR.

GOODSMVT_ITEM_I-ENTRY_QNT = ITAB-ENTRY_QNT.

GOODSMVT_ITEM_I-ITEM_TEXT = ITAB-MENGE.

SELECT SINGLE * FROM MARA WHERE MATNR = ITAB-MATNR.

IF SY-SUBRC = 0.

GOODSMVT_ITEM_I-ENTRY_UOM = MARA-MEINS.

ENDIF.

APPEND GOODSMVT_ITEM_I.

ENDLOOP.

GOODSMVT_CODE_H-GM_CODE = '05'.

TESTRUN_H = SPACE.

CALL FUNCTION 'BAPI_GOODSMVT_CREATE'

EXPORTING

GOODSMVT_HEADER = GOODSMVT_HEADER_H

GOODSMVT_CODE = GOODSMVT_CODE_H

* TESTRUN = 'X'

IMPORTING

* GOODSMVT_HEADRET =

MATERIALDOCUMENT = MATERIALDOCUMENT_O

MATDOCUMENTYEAR = DOC_YEAR

TABLES

GOODSMVT_ITEM = GOODSMVT_ITEM_I

* GOODSMVT_SERIALNUMBER =

RETURN = RETURN_O .

LEAVE TO LIST-PROCESSING.

WRITE:/ MATERIALDOCUMENT_O,

/ DOC_YEAR.

LOOP AT RETURN_O.

WRITE: / RETURN_O-MESSAGE,

/ RETURN_O-MESSAGE_V1,



/ RETURN_O-MESSAGE_V4.

ENDLOOP.

IF SY-SUBRC NE 0.

COMMIT WORK.

ENDIF.

No comments:

S U N D A Y , M A Y 1 8 , 2 0 0 8

To Change values of any database table directly in

debuging

Step I: Display any table (E.g.: T001L) entries available with the help

of transaction code SE16.




Step II: Select any rows and click on display button in toolbar.

Step III: Type /H in command field and press enter once. It will switch

on debugging.

Step IV:

Step V: Again Press Enter, following screen will come. Put one field

names as code and press enter. Change the value of code from SHOW

to EDIT and click on Change button.

Step VI: Now Click on Execute button (Run to cursor) or press F8.

Step VII: Now display entry will come in change mode. It will allow

changing any field value and saving any value.

Note: All Foreign Key checks will be applied.

No comments:

ALV Function Modules Documentation

Function group : SALV

REUSE_ALV_COMMENTARY_WRITE List body comment block output

REUSE_ALV_EVENTS_GET Returns table of possible events for a list

type

REUSE_ALV_EVENTS_TRANSFER

REUSE_ALV_EVENT_NAMES_GET Returns table of constant names of

possible events for a list type

REUSE_ALV_FIELDCATALOG_MERGE Create field catalog from

dictionary structure or internal table

REUSE_ALV_HIERSEQ_LIST_DISPLAY Hierarchical sequential list

output

REUSE_ALV_LIST_DISPLAY Output a simple list (single line or several

lines)

REUSE_ALV_LIST_LAYOUT_INFO_GET Read current ALV list

information

REUSE_ALV_LIST_LAYOUT_INFO_SET Set current ALV list information

REUSE_ALV_VARIANT_DEFAULT_GET Read default display variant

(description only, w/o field catalog)

REUSE_ALV_VARIANT_F4 Display variant selection dialog box

Function group:SLVC_FULLSCREEN

REUSE_ALV_GRID_COMMENTARY_SET

REUSE_ALV_GRID_DISPLAY Output of a simple list (single-line)

REUSE_ALV_GRID_DISPLAY_LVC

REUSE_ALV_GRID_LAYOUT_INFO_GET Read current ALV list

information

REUSE_ALV_GRID_LAYOUT_INFO_SET Set current ALV list

information

Function REUSE_ALV_LIST_DISPLAY

This module outputs an internal table with any structure as a



formatted one-line or multiple-line list.

PRINCIPLE:

Pass an internal table with the set of output information

Pass a structure with general list layout details

Pass a field catalogue as an internal table

The field catalogue describes the fields to be output in the list.

Exporting Parameters

I_INTERFACE_CHECK = ' '

2 I_BYPASSING_BUFFER =

3 I_BUFFER_ACTIVE = ' '

4 I_CALLBACK_PROGRAM = ' '

5 I_CALLBACK_PF_STATUS_SET = ' '

6 I_CALLBACK_USER_COMMAND = ' '

7 I_STRUCTURE_NAME =

8 IS_LAYOUT =

9 IT_FIELDCAT =

IT_EXCLUDING =

11 IT_SPECIAL_GROUPS =

12 IT_SORT =

13 IT_FILTER =

14 IS_SEL_HIDE =

15 I_DEFAULT = 'X'

16 I_SAVE = ' '

17 IS_VARIANT =

18 IT_EVENTS =

19 IT_EVENT_EXIT =

20 IS_PRINT =

21 IS_REPREP_ID =

22 I_SCREEN_START_COLUMN = 0

23 I_SCREEN_START_LINE = 0

24 I_SCREEN_END_COLUMN = 0

25 I_SCREEN_END_LINE = 0

Import & Table parameters

IMPORTING

E_EXIT_CAUSED_BY_CALLER =

ES_EXIT_CAUSED_BY_USER =

TABLES

T_OUTTAB =

EXCEPTIONS

PROGRAM_ERROR = 1

OTHERS

Though the ALV function module needs 25-30 parameters to be

passed, a simple report with ALV just requires these:

CALL FUNCTION 'REUSE_ALV_LIST_DISPLAY'

EXPORTING

I_CALLBACK_PROGRAM = ' '

TABLES

T_OUTTAB =

EXCEPTIONS

PROGRAM_ERROR = 1

OTHERS = 2.



PARAMETERS TO BE PASSED TO THE STANDARD ALV FUNCTION

MODULE

I_CALLBACK_PROGRAM

Program which calls the function module and contains the exit

routines. It must be a Report, Function group, Module pool or Form

routine pool (not an Include).

Note: Never pass SY-REPID directly in the interface. If the desired

program name is in SY-REPID, it must be assigned to an intermediate

variable which is then passed to the interface.

IT_FIELCAT - Field catalog with field descriptions

The field catalog for the output table is built-up in the caller's

coding. The build-up can be completely or partially automated by

calling the following function module

REUSE_ALV_FIELDCATALOG_MERGE

A field catalog need not be built-up and passed explicitly only under

the following conditions:

The internal table to be output has the same structure as a Data

Dictionary structure which is referred to in the internal table

declaration using LIKE or INCLUDE STRUCTURE.

All fields in this structure are to be output

The structure name is passed to ALV in the parameter

I_STRUCTURE_NAME.

Parameters to be passed

Positioning

row_pos (row position) value set: 0, 1 - 3

col_pos (column position) value set: 0, 1 60

Identification

fieldname (field name)

tabname (internal output table)

Data Dictionary reference

ref_fieldname (reference field name)

ref_tabname (reference table/structure field name)

Link to currency unit

cfieldname (currency unit field name)

ctabname (internal currency unit field output table)

Link to measurement unit

qfieldname (measurement unit field name)

qtabname (internal measurement unit field output table)

Column output options

outputlen (column width)

key (key column)

key_sel (hideable key column)

no_out (field in field list)

emphasize (highlight columns in color)

value set: SPACE, 'X' or 'Cxyz' (x:'1'-'9'; y,z: '0'=off '1'=on)

hotspot (column as hotspot)

fix_column (fix column)

do_sum (sum over column)

no_sum (sums forbidden)

Column output options (contd.)

input (column ready for input)

icon

symbol Texts



just (justification) value set: SPACE, 'R', 'L', 'C'

lzero (leading zeros)

no_sign (no +/- sign )

no_zero (suppress zeros)

edit_mask (field formatting) value set: SPACE, template

Texts

The texts are taken from the Data Dictionary for fields with a Data

Dictionary reference. If this is not desired, the text parameters can

also be specified. The Data Dictionary texts are then ignored.

seltext_l (long field label)

seltext_m (medium field label)

seltext_s (short field label)

reptext_ddic (header)

The specified text is not necessarily output in the list, an optimum

among all texts is sought

ddictxt (specify text)

value set: SPACE, 'L', 'M', 'S'

Parameters for program fields without Data Dictionary reference

datatype (data type ) value set: SPACE, Data Dictionary data type

ddic_outputlen (external output length) value set: 0 (initial), n

intlen (internal output length)value set: 0 (initial), n

rollname (data element) value set: SPACE, Data Dictionary data

element name

Priority rule:Entries in the field catalog have priority over differing

entries in the Data Dictionary.The following entries are usually

sufficient for internal table fields without a reference to the Data

Dictionary

1 Fieldname 2 Outputlen

3 Datatype 4 seltext_s

5 seltext_m 6 seltext_l

If the parameters SELTEXT_S, SELTEXT_M, SELTEXT_L, and

REPTEXT_DDIC contain appropriate field labels, the program field

column headers are also adjusted appropriately when the column

width changes.

Defaults :

The following entries are usually sufficient for internal table fields

with a reference to a field defined in the Data Dictionary :

fieldname

ref_tabname

ALV gets the remaining information from the Data Dictionary.

If no relative column position (COL_POS) is specified, the fields are

output in the list in the order in which they were added to the field

catalog.

REF_FIELDNAME need only be specified when the name of the internal

table field differs from the name of the referred Data Dictionary field.

Information which is explicitly entered in the field catalog is not

overwritten by information from the Data Dictionary.

I_STRUCTURE_NAME

If the internal output table is defined via an ABAP/4 Dictionary

structure (INCLUDE STRUCTURE struct or LIKE struct), the field



catalog can be built-up automatically by passing the structure name.

IS_LAYOUT -List layout specifications

The parameters are described under the following headers:

Display options

Totals

Interaction

Detail screen

Display variants (only for hierarchical lists)

Color

Other

Display options

colwidth_optimize

no_colhead

zebra

no_vline

no_min_linesize

max_linesize

Exceptions

lights_fieldname value set: SPACE, internal output table field name

lights_tabname value set: SPACE, internal output table name

lights_rollname value set: SPACE, data element name

lights_condense value set: SPACE, 'X'

Totals

no_sumchoice value set: SPACE, 'X'

no_totalline value set: SPACE, 'X'

no_subchoice value set: SPACE, 'X'

no_subtotals value set: SPACE, 'X'

totals_only value set: SPACE, 'X'

totals_text value set: SPACE, string(max.60)

subtotals_text value set: SPACE, string(max.60)

numc_sum value set: SPACE, 'X'

Interaction

box_fieldname value set: SPACE, internal output table field name

box_tabname value set: SPACE, internal output table name

no_input value set: SPACE, 'X'

expand_fieldname value set: SPACE, internal header table field

name

f2code value set: SPACE, function code

confirmation_prompt value set: SPACE, 'X'

key_hotspot value set: SPACE, 'X'

no_keyfix value set: SPACE, 'X'

get_selinfos value set: SPACE, 'X'

Detail screen

detail_popup value set: SPACE, 'X'

detail_initial_lines value set: SPACE, 'X'

detail_titlebar value set: SPACE, string(max.30)

Display variants & color

header_text value set: SPACE, CHAR(20)



item_text value set: SPACE, CHAR(20)

item_default value set: SPACE, 'X'

info_fieldname value set: SPACE, internal output table field name

coltab_fieldname value set: SPACE, internal output table field name

IT_SORT

The caller specifies the sorting and/or subtotalling of the basic list

in the internal table IT_SORT.

This internal table has the following fields

Spos Sort sequence

Fieldname Internal output table field name

Tabname Name of the internal output table

Up 'X' = sort in ascending order

Down 'X' = sort in descending order

Subtot 'X' = subtotal at group value change

group '* ' = new page at group value change

'UL' = underline at group value change

IT_EVENTS

This table tells ALV which events are processed by the caller by

CALLBACK.

The table of possible events per list type can be initialized using the

module REUSE_ALV_EVENTS_GET.

You can display the names of the constants in the type pools SLIS

which represent the individual events using the individual test

function in the function moduleREUSE_ALV_EVENT_NAMES_GET. Only

events with a form routine name are processed.

The table structure contains the fields:

IT_EVENTS-NAME-Name of the Callback event.

Action :

USER_COMMAND

PF_STATUS_SET

ITEM_DATA_EXPAND

List processing events :

TOP_OF_LIST

END_OF_LIST

END_OF_PAGE

TOP_OF_PAGE

TOP_OF_COVERPAGE

END_OF_COVERPAGE

IT_EVENTS-FORM - Name of the form routine which should be called

in the calling program at the event.

I_CALLBACK_USER_COMMAND

EXIT routine for command handling

Passing an EXIT routine tells ALV that the application wants to react

to certain function codes itself. These are general function codes

which ALV does not recognize (not ALV standard functions) and which

were defined and set by an application status.

FORM user_command USING r_ucomm LIKE sy-ucomm rs_selfield TYPE

slis_selfield.

The parameter R_UCOMM contains the function code called.

IT_EVENT_EXIT



Table for passing ALV standard function codes, to return control to

the user before and/or after execution with the callback event

USER_COMMAND.

The table fields are as follows:

ucomm

before

after

I_CALLBACK_PF_STATUS_ST

Passing an EXIT routine tells the ALV that the caller wants to set his

or her own user status. In this case, the default ALV status is not set.

The form routine interface must be defined as follows:

FORM set_pf_status USING rt_extab TYPE slis_t_extab

The table RT_EXTAB contains those function codes that are hidden

on the standard interface.

The structure RS_SELFIELD contains information:

tabname : internal output table name

tabindex : internal output table index

fieldname: field name of cursor position

sel_tab_field: cell name of cursor position (internal ALV table name

field

endsum : cursor is on the final total row

sumindex : if >0, the cursor is on a subtotal row

value : field value on the list

refresh : (exporting) list is to be refreshed

col_stable:(exporting) keep column positions in refresh

row_stable:(exporting) keep row positions in refresh

exit :(exporting) leave list (and ALV)

before_action: jump before performing standard action

after_action : jump after performing standard action, before

creating list

ignore_multi : internal use

IT_FILTER

Filter criteria for first list output

Filter criteria which result, e.g. from explicitly loading an initial

display variant, can be passed to list output in this parameter. This

table should never be built-up 'manually'.

I_DEFAULT

Initial variant logic active/inactive.

Prerequisite: The parameter IS_VARIANT has the appropriate value

Value Range

SPACE = no initial variant can be defined 'X' = initial variant can be

defined

Default SPACE

I_SAVE - variants can be saved

Value Range

' ' = display variants cannot be saved



'X' = standard save

'U' = only user-specific saving

'A' = standard and user-specific saving

IS_VARIANT

This structure is only relevant if display variants are to be saved

and/or read

The access path must be specified in the fields

REPORT (required field),

HANDLE (optional) unique user-assigned CHAR(4) field

LOG_GROUP (optional)

I_INTERFACE_CHECK

To avoid overloading list output with interface consistency checks,

they are only made in an extra call mode.

If this parameter is 'X', the consistency of the interface is checked

when the function module is called, and an error log is output.

This parameter should only be set for development test purposes

(e.g. in debugging).

The interface check can also be made on the results list by entering

the function code &SOS.

IS_PRINT

Print information

Print control parameter

PRINT

NO_PRINT_SELINFOS

NO_COVERPAGE

NO_NEW_PAGE

RESERVE_LINES

END_OF_PAGE

NO_PRINT_LISTINFOS

NO_CHANGE_PRINT_PARAMS

SCREEN_SETTINGS

Coordinates for list in dialog box

Only to be used if the list is output in a popup.

IT_SCREEN_START_COLUMN

x coordinate of the top left-hand corner of the popup.

IT_SCREEN_END_COLUMN

x coordinate of the bottom right-hand corner of the popup.

Coordinates for list in dialog box

Only used if the list is output in a popup.

IT_SCREEN_START_LINE

y coordinate of the top left-hand corner of the popup.

IT_SCREEN_END_LINE

y coordinate of the bottom right-hand corner of the popup.

E_EXIT_CAUSED_BY_CALLER

Delete list in CALLBACK_USER_COMMAND

Parameter which states whether the caller left the list (SELFIELD-

EXIT = 'X') in CALLBACK USER_COMMAND

ES_EXIT_CAUSED_BY_USER

How the user left the list

If one of the ALV standard function codes for 'Back', 'Cancel' or 'Exit'

occurs, the current list is discarded and the ALV function module





ends. In this case the exporting structure ES_EXIT_CAUSED_BY_USER

contains one of the following flags:

ES_EXIT_CAUSED_BY_USER-BACK = 'X

'Back' occurred

ES_EXIT_CAUSED_BY_USER-CANCEL = 'X'

'Cancel' occurred

ES_EXIT_CAUSED_BY_USER-EXIT = 'X'

'Exit' occurred

The function which occured determines the further navigation in the

application.

T_OUTTAB

Table with data to be displayed

This table can contain more fields than are relevant for the list

output (display fields and field list). Only the fields named in field

catalog and the layout structure are used for the list output. Other

internal table fields are ignored.

If the internal table is defined in the calling program without a

header, no F1 help is possible in the list.

REUSE_ALV_LIST_DISPLAY EXCEPTIONS

Program errors

Exception type

If the exception is not handled by the calling program, the following

applies:(X) an error message is sent.( ) a termination message is

sent.( ) a runtime error occurs.

No comments:

F R I D A Y , M A Y 1 6 , 2 0 0 8

DEFINING THE LOCAL PRINTER AS OUTPUT DEVICE

IN SAP

DEFINING THE LOCAL PRINTER AS OUTPUT DEVICE IN SAP

STEP1. T-SPAT OUTPUT DEVICES Create In device type field

,keep as original (means system default value for this field) ,

Step2. access method tab: values in filed host spool access method

= F

And in host printer = __DEFAULT

STEP3 SAVE AND THEN GIVE THE PRINTOUT WITH THE SHORT NAME

OF

DEVICE CREATED

No comments:




Sap Script Version Management

Problem :can we roll back to an older version in sap scripts ?suppose i

have made some changes in the existing code for the Script ,so i end

up getting a revised version. but later i'm being told to get back to

the older version . is it possible to activate the older version for SAP

Scripts .?

Solution: Follow the steps..1. In production, execute the program

RSTXSCRP,in sel.scrren - Object Name : give ur script namemode :

EXPORTdataset name : blank now execute,2. It will ask for a

filename, save the file as .TXT

3. In Devlopment, execute the same program RSTXSCRP,in sel.scrren

- Object Name : give ur script namemode : IMPORTdataset name :

blank now execute,4. It will ask for a filename, give the same file

which u have transfered from PROD and execute.....

As a result of above solution , we can copy the live sapscript working

in production to our developed sapscript in development and vice

cersa , this will make sure that we have both the versions same . this

is my answers to sap not providing version management for

sapscripts

No comments:

Home

Subscribe to: Posts (Atom)

ABAP Progamming

Hi All, Welcome to ABAP Programming Blog

abap_4 programming.pdf

Documents