|
Functionality
This function module is used for creating and changing functionallocations. Its functions correspond to the function modulesBAPI_FUNCLOC_CREATE and BAPI_FUNCLOC_CHANGE.
A multilingual short- and long text processing (creation/changing/deletion) is also possible.
The function module can be used for mass processing and works accordingto the "all or nothing" principle. This means, either you can create /change all the functional locations or you cannot create / change anyfunctional locations. Notes
The data for a functional location is shared between the followingtables:
CT_DATA
CT_DATAX
IT_DESCRIPT
IT_LONGTEXT
All the tables contain a TA_GUID field. The data for a functionallocation can be determined through this field. There is exactly oneCT_DATA- and CT_DATAX record for each functional location. However,there can be more than one IT_DESCRIPT- and IT_LONGTEXT records. Description
This structure contains all the master data of a functional location.It unifies the import parameters of the function modulesBAPI_FUNCLOC_CREATE and BAPI_FUNCLOC_CHANGE.
It contains the following structures:
BAPI_ITOB
BAPI_ITOB_FL_ONLY
For more information, see the documentation of the corresponding importparameters in the function modules BAPI_FUNCLOC_CREATE andBAPI_FUNCLOC_CHANGE.
The following fields are also included:
TA_GUID
FUNCLOC_EXT
FUNCLOC_INT
LABELING_SYSTEM
MDM_FLAG
WORK_CTR_EXTERN
WORK_CTR_PLANT
The field TA_GUID is used to determine the data for a functionallocation using the various tables.
The FUNCLOC_EXT field contains the key of the functional location. Akey must always be specified.
The LABELING_SYSTEM field specifies for what indicator system theexternal key is valid. If you are not using the alternative indicator,leave this field initial.
If no functional location can be determined for the field combinationFUNCLOC_EXT and LABELING_SYSTEM, the system tries to create a newfunctional location. Otherwise the functional location is updated.
The FUNCLOC_INT field contains the internal key of the created/changedfunctional location. If the alternative indicator is not activated,then the content of the FUNCLOC_INT and FUNCLOC_EXT fields isidentical.
If the MDM_FLAG field is set, then special MDM coding is run.
In the WRK_CTR_EXTERN and WRK_CTR_PLANT fields, the externaldescription and the value of the responsible work center are stored.The system uses this data to determine the internal description of theresponsible work center (field WORK_CTR ). If the system cannot findany internal description from the external description, then theinternal description is initialized. That means that the WORK_CTR fielddoes not need to be filled before being called up. Description
This structure corresponds to the structures BAPI_ITOBX andBAPI_ITOBX_FL_ONLY.
Each parameter in CT_DATA has a corresponding "selection parameter".Only the fields marked here with "X" are used for changing the data.
Example :
You want to update a functional location with data from a sourcesystem. In the source system however, the field NN cannot bemaintained. Field NN is maintained in the target system (R/3).
The field NN is always delivered from the source system as initial, andthis initial value should not overwrite the value maintained in thetarget system. This is achieved by setting the corresponding "selectionparameter" to initial. Description
Short texts/long texts can be created/changed/deleted in multiplelanguages for a functional locations:
The DELETE_DESCRIPT field specifies whether or not the short textshould be deleted.
The DELETE_LONGTEXT field specifies whether the long text belonging tothe short text should be deleted.
In R/3, you cannot have a long text for the header of a functionallocation without a short text. If the DELETE_DESCRIPT field is set, butthe DELETE_LONGTEXT field is not set, then the short text is justinitialized but not deleted.
If you want to delete the long text belonging to a short text, all youhave to do is set the IT_DESCRIPT-DELETE_LONGTEXT field. You do nothave to specify the long text using the IT_LONGTEXT structure as well. Description
For a functional location, short texts/long texts can becreated/changed/deleted in several languages.
You cannot change individual lines of existing long texts. Changing along text means replacing the existing long text with the long textprovided.
The field DELETE_LONGTEXT specifies whether the long text should bedeleted. The field value for the first line of the long text determineswhether or not the long text should be deleted. If you want to deletethe long text for the header of the functional location, you just haveto set the field IT_DESCRIPT-DELETE_LONGTEXT; you do not have to enterthe long text as well.
INCLUDE BAPI_RETURN OBJECT DOKU ID TX LANGUAGE EN |