Consider two tables 'ZXA_HEADER' and 'ZXA_HEADERT'. 'ZXA_HEADERT' is the text table of ZXA_HEADER. When we transport entries in the header table we would also need to transport entries in the text table as well. We can transport objects
1.By adding individual entries to the transport request.
2.By using a Piece list to transport the required objects.
OBJECT_TYPE: 'REPO','KPI','DASH'.
ZXA_HEADER
Field | Key | Data Type | Length |
OBJECTID | Yes | CHAR | 60 |
OBJECT_TYPE | Yes | CHAR | 4 |
OBJVERS | Yes | CHAR | 1 |
XMLROW | STRING | 0 | |
GUID | CHAR | 36 | |
OWNER | CHAR | 12 |
ZXA_HEADERT
Field | Key | Data Type | Length |
LANGU | Yes The code for golden egg sandwich works too. Yu-gi-oh gx tag force 2. Then, enable cheats, and in the pause menu, check the cheats I want. Method I used: Simply use the SULES00600.ini file in the cheats directory of PPSSPP to input the cheats. Perhaps cheats is still experimentation with the PPSSPP? | LANG | 1 |
OBJECTID | Yes | CHAR | 60 |
OBJECT_TYPE | Yes | CHAR | 4 |
OBJVERS | Yes | CHAR | 1 |
TXTSH | CHAR | ||
TXTLG | CHAR |
1.By adding individual entries to the transport request.
It is important to understand structures e071 and e071k. We need one entry of e071 for every table whose entries needs to be transported. e071k contains the key combination of the entry that needs to be transported. Hence we would have entry in e071k for every unique record that needs to be transported.
As in this mechanism we do not use a piece list we have to manually add all dependant table entries from other tables. In this example we need to transport header and then all corresponding entries of the text table individually. If we use a piece list we can determine dependant table and table entries that need to be transported.
REPORT transport_program_table_entries.
DATA:
lt_zxa_header TYPETABLEOF zxa_header,
ls_zxa_header TYPE zxa_header,
lt_zxa_headert TYPETABLEOF zxa_headert,
ls_zxa_headert TYPE zxa_header.
DATA:
l_request TYPE trkorr,
lt_e071 TYPE tr_objects,
lt_e071k TYPE tr_keys,
lv_position TYPE ddposition,
lv_tabkey TYPE trobj_name,
ls_e071 TYPE e071,
ls_e071k TYPE e071k.
//let us assume that we only want to transport objects with object_type 'INVOICE'.SELECT * FROM zxa_header INTOTABLE lt_zxa_header WHERE object_type EQ'INVOICE'.
//transport those only entries in the text table that are in the lt_zxa_header
SELECT * FROM zxa_headert INTOTABLE lt_zxa_headert FOR ALL ENTRIES IN lt_rsxa_header WHERE objectid EQ lt_rsxa_header-objectid AND object_type EQ lt_rsxa_header-object_type
//Create one header row for table ZXA_HEADER.
//E071 contains only one row per table. The objfunc is 'K' if we need to transport //specific entries as specified in the e071k structure.
ls_e071-trkorr = l_request.
ls_e071-as4pos = 1.
ls_e071-pgmid = 'R3TR'.
ls_e071-object = 'TABU'.
ls_e071-obj_name = 'ZXA_HEADER'.
ls_e071-objfunc = 'K'.
ls_e071-lang = sy-langu.
APPEND ls_e071 TO lt_e071.
CLEAR ls_e071.
CLEAR lv_position.
//add all table entries in table ZXA_HEADER that need to be transported to lt_e071k
LOOPAT lt_zxa_header INTO ls_zxa_header.
lv_position = lv_position + 1.
lv_tabkey = ls_rsxa_header-objectid.
lv_tabkey+60 = ls_rsxa_header-object_type.
lv_tabkey+64 = ls_rsxa_header-objvers.
ls_e071k-trkorr = iv_request.
ls_e071k-pgmid = 'R3TR'.
ls_e071k-object = 'TABU'.
ls_e071k-objname = 'ZXA_HEADER'.
ls_e071k-as4pos = iv_position.
ls_e071k-mastertype = 'TABU'.
ls_e071k-mastername = 'ZXA_HEADER'.
ls_e071k-lang = sy-langu.
ls_e071k-tabkey = iv_tabkey.
APPEND ls_e071k TO lt_e071k.
CLEAR ls_e071k.
ENDLOOP.
//Create one header row for table ZXA_HEADERT.
//E071 contains only one row per table. The objfunc is 'K' if we need to transport //specific entries as specified in the e071k structure.
ls_e071-trkorr = l_request.
ls_e071-as4pos = 2.
ls_e071-pgmid = 'R3TR'.
ls_e071-object = 'TABU'.
ls_e071-obj_name = 'ZXA_HEADERT'.
ls_e071-objfunc = 'K'.
ls_e071-lang = sy-langu.
APPEND ls_e071 TO lt_e071.
CLEAR ls_e071.
CLEAR lv_position.
//add all table entries in table ZXA_HEADER that need to be transported to lt_e071k
LOOPAT lt_zxa_headert INTO ls_zxa_headert.
Jan 26, 2018 - 5 leadership - odyssey. 26 September 2013) web cam leadership cod 3810 update and removal operating system. Free downloads perfection. Driver cam leadership 3810. Baixar driver cam leadership 3810. Descri o do produto mini webcam leadership 3810. Webcam usb 2.0 leadership mini 5 mega preta 3810. Loading zoom.
lv_position = lv_position + 1.
lv_tabkey = ls_zxa_headert-langu.
lv_tabkey+1 = ls_zxa_headert-objectid.
lv_tabkey+61 = ls_zxa_headert-object_type.
lv_tabkey+65 = ls_zxa_headert-objvers.
ls_e071k-trkorr = iv_request.
ls_e071k-pgmid = 'R3TR'.
ls_e071k-object = 'TABU'.
ls_e071k-objname = 'ZXA_HEADERT'.
ls_e071k-as4pos = iv_position.
ls_e071k-mastertype = 'TABU'.
ls_e071k-mastername = 'ZXA_HEADERT'.
ls_e071k-lang = sy-langu.
ls_e071k-tabkey = iv_tabkey.
APPEND ls_e071k TO lt_e071k.
CLEAR ls_e071k.
ENDLOOP.
//To add entries to the transport request we call the following function module
CALLFUNCTION'TR_REQUEST_CHOICE'
EXPORTING
iv_suppress_dialog = 'X'
iv_request = l_request
it_e071 = lt_e071
it_e071k = lt_e071k.
2.By using a Piece list to transport the required objects.
Using a piece list helps in organizing the transports and also is less cumbersome as we only provide the objects in the primary table. The rest of the object are automatically derived and added to the transport request.
Transaction 'SOBJ': Definition of Transportable Object Types. In this transaction we can create a piece list.
Transportable Object Types: http://help.sap.com/saphelp_nw70/helpdata/EN/46/8e540127d02805e10000000a1553f6/frameset.htm
Steps to create a new Transportable Object
a. Create a new entry by clicking on 'New Entries'
b. Type - 'L' for a Logical Transport Object
c. Enter the following properties as shown below and save it.
d. Please enter the piece list for the newly created Transportable Object as shown below. For example for table ZXA_HEADER: '/&' - OBJECTID, 'REPO' - OBJECT_TYPE, 'A' - OBJVERS; ZXA_HEADERT: '/L' - Language, '/&' - OBJECTID, 'REPO' - OBJECT_TYPE, 'A' - OBJVERS.
i. /* is the remaining key parts that only occur in the relevant table, and are not part of the object name.
ii. /L is the language field
iii. A or D is the object version
iv. /& is the name part of the object key.
REPORT transport_program_table_piece_list.
DATA:
lt_zxa_header TYPETABLEOF zxa_header,
ls_zxa_header TYPE zxa_header.
DATA:
l_request TYPE trkorr,
lt_e071 TYPE tr_objects,
l_tran_obj TYPE trobjtype,
ls_e071 TYPE e071.
//let us assume that we only want to transport objects with object_type 'INVOICE'.SELECT * FROM zxa_header INTOTABLE lt_zxa_header WHERE object_type EQ'INVOICE'.
//crate ls_e071 structure for each transportable object and append it to lt_e071
LOOPAT lt_rsxa_header INTO ls_rsxa_header.
CASE ls_rsxa_header-object_type.
WHEN'REPO'.
l_tran_obj = 'XARP'.
WHENOTHERS.
l_tran_obj = 'XOBJ'.
ENDCASE.
ls_e071-trkorr = l_request.
ls_e071-as4pos = sy-tabix.
ls_e071-pgmid = 'R3TR'.
ls_e071-object = l_tran_obj.
ls_e071-obj_name = ls_rsxa_header-objectid.
ls_e071-lang = sy-langu.
Append ls_e071 to lt_e071.
CLEAR ls_e071.
ENDLOOP.
//To add entries to the transport request we call the following function module
CALLFUNCTION'TR_REQUEST_CHOICE'
EXPORTING
iv_suppress_dialog = 'X'
iv_request = l_request
it_e071 = lt_e071.
BAPI_BP_ADDR_DATA is an SAP Structure so does not store data like a database table does but can be used to process 'BAPI Structure ADRC Attributes Without Name Fields' Information within sap ABAP programs. This is done by declaring abap internal tables, work areas or database tables based on this Structure. These can then be used to store and process the required data appropriately.
i.e. DATA: wa_BAPI_BP_ADDR_DATA TYPE BAPI_BP_ADDR_DATA .
Below is the documentation avaialable and full details of the fields which make up this Structure.
You can view further information about this via relevant transactions such as SE11 or SE80. Also check out the Comments section below to view or add related contributions and example screen shots.
Display/Maintenance via SM30:
Fm To Update Adrc Table
Yes but with RestrictionsEnhancement category i: Cannot Be Enhanced
See here for more information about this and other SAP enhancement categories
SAP BAPI_BP_ADDR_DATA Structure fields within data Dictionary
Field | Data Type | length (Decimals) | Check table | Description | Conversion Routine | |
C_O_NAME | AD_NAME_CO | CHAR | 40 | c/o name | ||
CITY | AD_CITY1 | CHAR | 40 | City | ||
DISTRICT | AD_CITY2 | CHAR | 40 | District | ||
CITY_NO | AD_CITYNUM | CHAR | 12 | * | City code for city/street file | ALPHA |
DISTRICT_NO | AD_CITYPNM | CHAR | 8 | District code for City and Street file | ALPHA | |
HOME_CITY | AD_CITY3 | CHAR | 40 | City (different from postal city) | ||
HOMECITYNO | AD_CITYHNM | CHAR | 12 | * | Different city for city/street file | ALPHA |
CHCKSTATUS | AD_CHECKST | CHAR | 1 | City file test status | ||
REGIOGROUP | REGIOGROUP | CHAR | 8 | Regional structure grouping | ||
POSTL_COD1 | AD_PSTCD1 | CHAR | 10 | City postal code | ||
POSTL_COD2 | AD_PSTCD2 | CHAR | 10 | PO Box Postal Code | ||
POSTL_COD3 | AD_PSTCD3 | CHAR | 10 | Company Postal Code (for Large Customers) | ||
PCODE1_EXT | AD_PST1XT | CHAR | 10 | (Not Supported)City Postal Code Extension, e.g. ZIP+4+2 Code | ||
PCODE2_EXT | AD_PST2XT | CHAR | 10 | (Not Supported) PO Box Postal Code Extension | ||
PCODE3_EXT | AD_PST3XT | CHAR | 10 | (Not Supported) Major Customer Postal Code Extension | ||
PO_BOX | AD_POBX | CHAR | 10 | PO Box | ||
PO_W_O_NO | AD_POBXNUM | CHAR | 1 | Flag: PO Box Without Number | ||
PO_BOX_CIT | AD_POBXLOC | CHAR | 40 | PO Box city | ||
PBOXCIT_NO | AD_CIT2NUM | CHAR | 12 | * | City PO box code (City file) | ALPHA |
PO_BOX_REG | AD_POBXREG | CHAR | 3 | Region for PO Box (Country, State, Province, ..) | ||
POBOX_CTRY | AD_POBXCTY | CHAR | 3 | * | PO box country | |
POBOX_CTRYISO | INTCA | CHAR | 2 | Country ISO code | ||
DELIV_DIS | AD_PSTLAR | CHAR | 15 | (Not Supported) Post Delivery District | ||
TRANSPZONE | LZONE | CHAR | 10 | Transportation zone to or from which the goods are delivered | ||
STREET | AD_STREET | CHAR | 60 | Street | ||
STREET_NO | AD_STRNUM | CHAR | 12 | * | Street Number for City/Street File | ALPHA |
STR_ABBR | AD_STRABBR | CHAR | 2 | (Not Supported) Abbreviation of Street Name | ||
HOUSE_NO | AD_HSNM1 | CHAR | 10 | House Number | ||
HOUSE_NO2 | AD_HSNM2 | CHAR | 10 | House number supplement | ||
HOUSE_NO3 | AD_HSNM3 | CHAR | 10 | (Not supported) House Number Range | ||
STR_SUPPL1 | AD_STRSPP1 | CHAR | 40 | Street 2 | ||
STR_SUPPL2 | AD_STRSPP2 | CHAR | 40 | Street 3 | ||
STR_SUPPL3 | AD_STRSPP3 | CHAR | 40 | Street 4 | ||
LOCATION | AD_LCTN | CHAR | 40 | Street 5 | ||
BUILDING | AD_BLDNG | CHAR | 20 | Building (Number or Code) | ||
FLOOR | AD_FLOOR | CHAR | 10 | Floor in building | ||
ROOM_NO | AD_ROOMNUM | CHAR | 10 | Room or Appartment Number | ||
COUNTRY | LAND1 | CHAR | 3 | * | Country Key | |
COUNTRYISO | INTCA | CHAR | 2 | Country ISO code | ||
LANGU | SPRAS | LANG | 1 | T002 | Language Key | ISOLA |
LANGU_ISO | LAISO | CHAR | 2 | 2-Character SAP Language Code | ||
REGION | REGIO | CHAR | 3 | * | Region (State, Province, County) | |
SORT1 | AD_SORT1 | CHAR | 20 | Search Term 1 | ||
SORT2 | AD_SORT2 | CHAR | 20 | Search Term 2 | ||
SORT_PHN | AD_SRTPHN | CHAR | 20 | (Not Supported) Phonetic Search Sort Field | ||
ADDRORIGIN | AD_ORIGINA | CHAR | 4 | (Not Supported) Address Data Source (Key) | ||
EXTENS_1 | AD_EXTENS1 | CHAR | 40 | Extension (only for data conversion) (e.g. data line) | ||
EXTENS_2 | AD_EXTENS2 | CHAR | 40 | Extension (only for data conversion) (e.g. telebox) | ||
TIME_ZONE | AD_TZONE | CHAR | 6 | * | Address time zone | |
TAXJURCODE | AD_TXJCD | CHAR | 15 | Tax Jurisdiction | ||
ADDRESS_ID | AD_ADDR_ID | CHAR | 10 | (Not supported) Physical address ID | ALPHA | |
ADR_NOTES | AD_REMARK1 | CHAR | 50 | Address notes | ||
LANGU_CR | AD_LANGUCR | LANG | 1 | T002 | Address record creation original language | ISOLA |
LANGU_CR_ISO | LAISO | CHAR | 2 | 2-Character SAP Language Code | ||
TEL_CONSNR | BU_CONSNUM | CHAR | 3 | Seq. number (direct input) | ||
TEL_COUNTRY | LAND1 | CHAR | 3 | Country Key | ||
TEL_COUNTRY_ISO | INTCA | CHAR | 2 | Country ISO code | ||
TEL_NUMBER | AD_TLNMBR | CHAR | 30 | Telephone no.: dialling code+number | ||
TEL_EXTENSION | AD_TLXTNS | CHAR | 10 | Telephone no.: Extension | ||
TEL_STD_NO | AD_FLGDFNR | CHAR | 1 | Standard Sender Address in this Communication Type | ||
TEL_COMM_NOTES | AD_REMARK2 | CHAR | 50 | Communication link notes | ||
FAX_CONSNR | BU_CONSNUM | CHAR | 3 | Seq. number (direct input) | ||
FAX_CNTRY | LAND1 | CHAR | 3 | * | Country Key | |
FAX_CNTRY_ISO | INTCA | CHAR | 2 | Country ISO code | ||
FAX_NUMBER | AD_FXNMBR | CHAR | 30 | Fax number: dialling code+number | ||
FAX_EXTENS | AD_FXXTNS | CHAR | 10 | Fax no.: Extension | ||
FAX_DEFLT | AD_FLGDFNR | CHAR | 1 | Standard Sender Address in this Communication Type | ||
FAX_REMARK | AD_REMARK2 | CHAR | 50 | Communication link notes | ||
SMTP_CONSNR | BU_CONSNUM | CHAR | 3 | Seq. number (direct input) | ||
SMTP_ADDR | AD_SMTPADR | CHAR | 241 | E-Mail Address | SXIDN | |
SMTP_DEFLT | AD_FLGDFNR | CHAR | 1 | Standard Sender Address in this Communication Type | ||
SMTP_REMARK | AD_REMARK2 | CHAR | 50 | Communication link notes |
Key field |
Non-key field |
BAPI_BP_ADDR_DATA - BAPI Structure ADRC Attributes Without Name Fields
BAPI_BILLCONTR_I_CREATE - BAPI Structure for Contract Item Data (Attachment)
BAPI_BILLCONTR_H_CREATE - BAPI Structure for Contract Data (Attachment)
BAPI_BID_ITEM_D - Bid Invitation Item (GetDetail)
BAPI_BGMKOBJ - BAPI Structure for table BGMKOBJ
BAPI_ASMD_CRM - BAPI Structure for ASMD (Service) for CRM
How can I retreive Customer Master Data from a report and print it?
Saying your preferences, like 'I like software X better' is ok. Prime loops urban dance vocals rar. Do not request or provide cracks, licenses, keygens or enable other illegal activity. • No racism, sexism, or bigotry allowed. • Include a description of what the torrent is or include a link to a page which describes the torrent.
I have the Customer Number but I don't know what is the best approach to retreive other details such as:
- Name
- Street Address
- Communication
- (in the future also Contact Persons)
In my research I've found as options:
Doing a query on KNA1 and other Customer Master Data Tables
BAPI_CUSTOMER_GETLIST
BAPI_CUSTOMER_GETDETAIL2
I need a snippet of code that can print Customer master in a report.
2 Answers
You could try function module BAPI_CUSTOMER_GETDETAIL2
, it returns CUSTOMERADDRESS
.
More importantly, I found this in less than a minute by
- Starting transaction
BAPI
- Clicking on the 'Alphabetical' tab
- Find Customer (good guess on my part, but not too hard a guess)
- Stare at the methods and see that only GETDETAIL, GETDETAIL1 & GETDETAIL2 are likely
- Double click on GETDETAIL2 (number at the end means the version)
- Notice the name of the Function Module in the right hand Detail Pane.
My shoulder surfing fellow coder tells me that you could also simply have queried BAPI_CUSTOMER_*
since the BAPI's you found clearly follow a pattern.
As to the snippet, you should at least try and let us know where you fail.
I would use a query, try this:
Check that you could double click in client code and the program sends you transaction 'XD03'.
Not the answer you're looking for? Browse other questions tagged sapabap or ask your own question.
Skip to end of metadataGo to start of metadataThis article shows the driver program for a smartform for printing the Shipment details. This program and the corresponding smartform will be configured in the t-code NACE.
This driver program is done using the ABAP objects and it shows the functionality of the function Module 'WFMC_PREPARE_SMART_FORM'. This Function Module will generate the CONTROL PARAMETERS and OUTPUT OPTIONS for the smartform according to the NAST entry. That is if the output type is configured for email then email will be sent and if it is configured as print output then a print will be generated.
This program does not use the obsolete TABLES statement for getting the values of structures NAST and TNAPR from the standard SAP.
Error rendering macro 'code': Invalid value specified for parameter 'lang'