What are criterias to create Config. Scenarios and Comm Channels?

Suppose we have 10 interfaces of same kind - file to file , some of them are inbound some of them are outbound relatively to R/3.
Suppose also we have 15 File to Rfc , 5 rfc's to File .All they are interfaces communicating with external partners(that are not on our landscape)
I have few questions regarding the config in ID.
1. In the case above - what would be the criteria to create new Configuration Scenarios, how many are needed ?
2.Is it right to create Config Scenario for each Interface ?Or os it right to create all same kind if (e.g. file to file) under one Config Scenario?
3. what would be the criteria to create Communication Channels, how many are needed ?
4.Is it right approach to create 2 separate Comm channels recv/send for each separate interface?Or may be I can Reuse some communication channels from another already created interfaces - true or not?
I will appreciate your fast reply and also if you know what is the best practice..
Thanks !
Jon

Hi jon,
For the 15 File to RFC scenario u can have a Generic scenario to pick up the file and route it to the respective other scenario i.e design one common generic interface to poll the file and route it to 15 other scenario this reduces u to have onle one CC instead to have 15 communication channels and 15 receiver determinations from the file sender.
Have a look at this Blog.. <a href="/people/sravya.talanki2/blog/2005/08/16/configuring-generic-sender-file-cc-adapter Generic Sender File CC Adapter</a> By Sravya Talanki
also read thru the comments of this blog to get the clear picture...
also look at my wiki... <a href="https://wiki.sdn.sap.com/wiki/display/XI/SingleSenderFileCC4MultipleDirectories">Single Sender File CC 4 Multiple Directories</a>
Regards
San
Remember to set the thread to solved when you have received a solution there is a Way.

Similar Messages

What are the uses of MVC, Extension and how to create it for begineers pls

what are the uses of MVC, Extension and how to create it for begineers pls
dont give link for tutorials please explain ,
thank you,
Regards,
Jagrut BahratKumar Shukla

Hi,
Check out this link :
<a href="http://help.sap.com/saphelp_nw04/helpdata/en/0f/ab3a3c9ca75402e10000000a114084/content.htm">http://help.sap.com/saphelp_nw04/helpdata/en/0f/ab3a3c9ca75402e10000000a114084/content.htm</a>
It is the best possible explanation and documentation that you'll get.
Thanks,
Tatvagna.

What are the integration pts of RFX and Reverse Auctions & ways of creating

Hi Friends
What are the integration points of RFX and Reverse Auctions & ways of creating them
Regards
Surya
Edited by: surya K on Jan 14, 2009 4:56 AM

Hi Surya
You need to be more clear on the thread.
Please detail out what you are looking at
Whether you are trying to integrate SRM Bid Invitation O/P to SAP E-Sourcing RFx draft
or some other integration.
Please spell out clearly
Regards
Tridip Chakraborthy

What are differences between the target tablespace and the source tablespac

The IMPDP command create so manay errors. But the EXAMPLE tablespace is transported to the target database successfully. It seems that the transported tablespace is no difference with the source tablespace.
Why create so many errors?
How to avoid these errors?
What are differences between the target tablespace and the source tablespace?
Is this datapump action really successfull?
Thw following is the log output:
[oracle@hostp ~]$ impdp system/oracle dumpfile=user_dir:demo02.dmp tablespaces=example remap_tablespace=example:example
Import: Release 10.2.0.1.0 - Production on Sunday, 28 September, 2008 18:08:31
Copyright (c) 2003, 2005, Oracle. All rights reserved.
Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
With the Partitioning, OLAP and Data Mining options
Master table "SYSTEM"."SYS_IMPORT_TABLESPACE_01" successfully loaded/unloaded
Starting "SYSTEM"."SYS_IMPORT_TABLESPACE_01": system/******** dumpfile=user_dir:demo02.dmp tablespaces=example remap_tablespace=example:example
Processing object type TABLE_EXPORT/TABLE/TABLE
ORA-39117: Type needed to create table is not included in this operation. Failing sql is:
CREATE TABLE "OE"."CUSTOMERS" ("CUSTOMER_ID" NUMBER(6,0), "CUST_FIRST_NAME" VARCHAR2(20) CONSTRAINT "CUST_FNAME_NN" NOT NULL ENABLE, "CUST_LAST_NAME" VARCHAR2(20) CONSTRAINT "CUST_LNAME_NN" NOT NULL ENABLE, "CUST_ADDRESS" "OE"."CUST_ADDRESS_TYP" , "PHONE_NUMBERS" "OE"."PHONE_LIST_TYP" , "NLS_LANGUAGE" VARCHAR2(3), "NLS_TERRITORY" VARCHAR2(30), "CREDIT_LIMIT" NUMBER(9,2), "CUST_EMAIL" VARCHAR2(30), "ACCOUNT_MGR_ID" NU
ORA-39117: Type needed to create table is not included in this operation. Failing sql is:
ORA-39117: Type needed to create table is not included in this operation. Failing sql is:
CREATE TABLE "IX"."ORDERS_QUEUETABLE" ("Q_NAME" VARCHAR2(30), "MSGID" RAW(16), "CORRID" VARCHAR2(128), "PRIORITY" NUMBER, "STATE" NUMBER, "DELAY" TIMESTAMP (6), "EXPIRATION" NUMBER, "TIME_MANAGER_INFO" TIMESTAMP (6), "LOCAL_ORDER_NO" NUMBER, "CHAIN_NO" NUMBER, "CSCN" NUMBER, "DSCN" NUMBER, "ENQ_TIME" TIMESTAMP (6), "ENQ_UID" VARCHAR2(30), "ENQ_TID" VARCHAR2(30), "DEQ_TIME" TIMESTAMP (6), "DEQ_UID" VARCHAR2(30), "DEQ_
Processing object type TABLE_EXPORT/TABLE/TABLE_DATA
. . imported "SH"."CUSTOMERS" 9.850 MB 55500 rows
. . imported "SH"."SUPPLEMENTARY_DEMOGRAPHICS" 695.9 KB 4500 rows
. . imported "OE"."PRODUCT_DESCRIPTIONS" 2.379 MB 8640 rows
. . imported "SH"."SALES":"SALES_Q4_2001" 2.257 MB 69749 rows
. . imported "SH"."SALES":"SALES_Q1_1999" 2.070 MB 64186 rows
. . imported "SH"."SALES":"SALES_Q3_2001" 2.129 MB 65769 rows
. . imported "SH"."SALES":"SALES_Q1_2000" 2.011 MB 62197 rows
. . imported "SH"."SALES":"SALES_Q1_2001" 1.964 MB 60608 rows
. . imported "SH"."SALES":"SALES_Q2_2001" 2.050 MB 63292 rows
. . imported "SH"."SALES":"SALES_Q3_1999" 2.166 MB 67138 rows
Processing object type TABLE_EXPORT/TABLE/GRANT/OWNER_GRANT/OBJECT_GRANT
ORA-39083: Object type OBJECT_GRANT failed to create with error:
ORA-01917: user or role 'USER1' does not exist
Failing sql is:
GRANT SELECT ON "HR"."REGIONS" TO "USER1"
ORA-39083: Object type OBJECT_GRANT failed to create with error:
ORA-01917: user or role 'EXAM_03' does not exist
Failing sql is:
GRANT SELECT ON "HR"."REGIONS" TO "EXAM_03"
ORA-39083: Object type OBJECT_GRANT failed to create with error:
ORA-01917: user or role 'USER1' does not exist
Failing sql is:
GRANT SELECT ON "HR"."COUNTRIES" TO "USER1"
ORA-39083: Object type OBJECT_GRANT failed to create with error:
ORA-01917: user or role 'EXAM_03' does not exist
Failing sql is:
GRANT SELECT ON "HR"."COUNTRIES" TO "EXAM_03"
ORA-39083: Object type OBJECT_GRANT failed to create with error:
ORA-01917: user or role 'USER1' does not exist
Failing sql is:
GRANT SELECT ON "HR"."LOCATIONS" TO "USER1"
ORA-39083: Object type OBJECT_GRANT failed to create with error:
ORA-01917: user or role 'EXAM_03' does not exist
Failing sql is:
GRANT SELECT ON "HR"."LOCATIONS" TO "EXAM_03"
ORA-39083: Object type OBJECT_GRANT failed to create with error:
ORA-01917: user or role 'USER1' does not exist
Failing sql is:
GRANT SELECT ON "HR"."DEPARTMENTS" TO "USER1"
ORA-39083: Object type OBJECT_GRANT failed to create with error:
ORA-01917: user or role 'EXAM_03' does not exist
Failing sql is:
GRANT SELECT ON "HR"."DEPARTMENTS" TO "EXAM_03"
ORA-39083: Object type OBJECT_GRANT failed to create with error:
ORA-01917: user or role 'USER1' does not exist
Failing sql is:
GRANT SELECT ON "HR"."JOBS" TO "USER1"
ORA-39083: Object type OBJECT_GRANT failed to create with error:
ORA-01917: user or role 'EXAM_03' does not exist
Failing sql is:
GRANT SELECT ON "HR"."JOBS" TO "EXAM_03"
ORA-39083: Object type OBJECT_GRANT failed to create with error:
ORA-01917: user or role 'USER1' does not exist
Failing sql is:
GRANT SELECT ON "HR"."EMPLOYEES" TO "USER1"
ORA-39083: Object type OBJECT_GRANT failed to create with error:
ORA-01917: user or role 'EXAM_03' does not exist
Failing sql is:
GRANT SELECT ON "HR"."EMPLOYEES" TO "EXAM_03"
ORA-39083: Object type OBJECT_GRANT failed to create with error:
ORA-01917: user or role 'USER1' does not exist
Failing sql is:
GRANT SELECT ON "HR"."JOB_HISTORY" TO "USER1"
ORA-39083: Object type OBJECT_GRANT failed to create with error:
ORA-01917: user or role 'EXAM_03' does not exist
Failing sql is:
GRANT SELECT ON "HR"."JOB_HISTORY" TO "EXAM_03"
ORA-39112: Dependent object type OBJECT_GRANT:"OE" skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
ORA-39112: Dependent object type OBJECT_GRANT:"OE" skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
Processing object type TABLE_EXPORT/TABLE/INDEX/INDEX
ORA-39112: Dependent object type INDEX:"OE"."CUSTOMERS_PK" skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
ORA-39112: Dependent object type INDEX:"OE"."CUST_ACCOUNT_MANAGER_IX" skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
ORA-39112: Dependent object type INDEX:"OE"."CUST_LNAME_IX" skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
ORA-39112: Dependent object type INDEX:"OE"."CUST_EMAIL_IX" skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
ORA-39112: Dependent object type INDEX:"PM"."PRINTMEDIA_PK" skipped, base object type TABLE:"PM"."PRINT_MEDIA" creation failed
Processing object type TABLE_EXPORT/TABLE/CONSTRAINT/CONSTRAINT
ORA-39112: Dependent object type CONSTRAINT:"OE"."CUSTOMER_CREDIT_LIMIT_MAX" skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
ORA-39112: Dependent object type CONSTRAINT:"OE"."CUSTOMER_ID_MIN" skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
ORA-39112: Dependent object type CONSTRAINT:"OE"."CUSTOMERS_PK" skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
ORA-39112: Dependent object type CONSTRAINT:"PM"."PRINTMEDIA__PK" skipped, base object type TABLE:"PM"."PRINT_MEDIA" creation failed
ORA-39112: Dependent object type CONSTRAINT:"IX"."SYS_C005192" skipped, base object type TABLE:"IX"."ORDERS_QUEUETABLE" creation failed
Processing object type TABLE_EXPORT/TABLE/INDEX/STATISTICS/INDEX_STATISTICS
ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type INDEX:"OE"."CUSTOMERS_PK" creation failed
ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type INDEX:"OE"."CUST_ACCOUNT_MANAGER_IX" creation failed
ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type INDEX:"OE"."CUST_LNAME_IX" creation failed
ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type INDEX:"OE"."CUST_EMAIL_IX" creation failed
ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type INDEX:"PM"."PRINTMEDIA_PK" creation failed
Processing object type TABLE_EXPORT/TABLE/COMMENT
ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
Processing object type TABLE_EXPORT/TABLE/CONSTRAINT/REF_CONSTRAINT
ORA-39112: Dependent object type REF_CONSTRAINT:"OE"."CUSTOMERS_ACCOUNT_MANAGER_FK" skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
ORA-39083: Object type REF_CONSTRAINT failed to create with error:
ORA-00942: table or view does not exist
Failing sql is:
ALTER TABLE "OE"."ORDERS" ADD CONSTRAINT "ORDERS_CUSTOMER_ID_FK" FOREIGN KEY ("CUSTOMER_ID") REFERENCES "OE"."CUSTOMERS" ("CUSTOMER_ID") ON DELETE SET NULL ENABLE
ORA-39112: Dependent object type REF_CONSTRAINT:"PM"."PRINTMEDIA_FK" skipped, base object type TABLE:"PM"."PRINT_MEDIA" creation failed
Processing object type TABLE_EXPORT/TABLE/TRIGGER
ORA-39082: Object type TRIGGER:"HR"."SECURE_EMPLOYEES" created with compilation warnings
ORA-39082: Object type TRIGGER:"HR"."SECURE_EMPLOYEES" created with compilation warnings
ORA-39082: Object type TRIGGER:"HR"."UPDATE_JOB_HISTORY" created with compilation warnings
ORA-39082: Object type TRIGGER:"HR"."UPDATE_JOB_HISTORY" created with compilation warnings
Processing object type TABLE_EXPORT/TABLE/INDEX/FUNCTIONAL_AND_BITMAP/INDEX
ORA-39112: Dependent object type INDEX:"OE"."CUST_UPPER_NAME_IX" skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
Processing object type TABLE_EXPORT/TABLE/INDEX/STATISTICS/FUNCTIONAL_AND_BITMAP/INDEX_STATISTICS
ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type INDEX:"OE"."CUST_UPPER_NAME_IX" creation failed
Processing object type TABLE_EXPORT/TABLE/STATISTICS/TABLE_STATISTICS
ORA-39112: Dependent object type TABLE_STATISTICS skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
ORA-39112: Dependent object type TABLE_STATISTICS skipped, base object type TABLE:"PM"."PRINT_MEDIA" creation failed
ORA-39112: Dependent object type TABLE_STATISTICS skipped, base object type TABLE:"PM"."PRINT_MEDIA" creation failed
ORA-39112: Dependent object type TABLE_STATISTICS skipped, base object type TABLE:"IX"."ORDERS_QUEUETABLE" creation failed
Processing object type TABLE_EXPORT/TABLE/INDEX/DOMAIN_INDEX/INDEX
Processing object type TABLE_EXPORT/TABLE/POST_INSTANCE/PROCACT_INSTANCE
ORA-39112: Dependent object type PROCACT_INSTANCE skipped, base object type TABLE:"IX"."ORDERS_QUEUETABLE" creation failed
ORA-39083: Object type PROCACT_INSTANCE failed to create with error:
ORA-01403: no data found
ORA-01403: no data found
Failing sql is:
BEGIN
SYS.DBMS_AQ_IMP_INTERNAL.IMPORT_SIGNATURE_TABLE('AQ$_ORDERS_QUEUETABLE_G');COMMIT; END;
Processing object type TABLE_EXPORT/TABLE/POST_INSTANCE/PROCDEPOBJ
ORA-39112: Dependent object type PROCDEPOBJ:"IX"."AQ$_ORDERS_QUEUETABLE_V" skipped, base object type TABLE:"IX"."ORDERS_QUEUETABLE" creation failed
ORA-39112: Dependent object type PROCDEPOBJ:"IX"."ORDERS_QUEUE_N" skipped, base object type TABLE:"IX"."ORDERS_QUEUETABLE" creation failed
ORA-39112: Dependent object type PROCDEPOBJ:"IX"."ORDERS_QUEUE_R" skipped, base object type TABLE:"IX"."ORDERS_QUEUETABLE" creation failed
ORA-39112: Dependent object type PROCDEPOBJ:"IX"."AQ$_ORDERS_QUEUETABLE_E" skipped, base object type TABLE:"IX"."ORDERS_QUEUETABLE" creation failed
ORA-39112: Dependent object type PROCDEPOBJ:"IX"."ORDERS_QUEUE" skipped, base object type TABLE:"IX"."ORDERS_QUEUETABLE" creation failed
Job "SYSTEM"."SYS_IMPORT_TABLESPACE_01" completed with 63 error(s) at 18:09:14

Short of trying to then reverse-engineer the objects that are in the dump file (I believe Data Pump export files contain some XML representations of DDL in addition to various binary bits, making it potentially possible to try to scan the dump file for the object definitions), I would tend to assume that the export didn't include those type definitions.
Since it looks like you're trying to set up the sample schemas, is there a reason that you wouldn't just run the sample schema setup scripts on the destination database? Why are you using Data Pump in the first place?
Justin

How to find out what are the interfaces used for Job and Job Codes

HI All,
I just wanted to know how do we find out what are the interfaces used for Job and Job codes .
Thanks In Advance
Sunny

Hi,
Here is an idea for your request.
Basically you can create a simple query on multiprovider 0TCT_MC01.
Filter: you can use a variable for restriction of time ( calday, or calmonth) since you should be interested for a time period.
Choose following characters into your objects:
InfoProvider ( 0TCTIFPROV ) - you can create a variable for choosing infoprovider before query runs.
*Tp.[Type of BI Application Object] 0TCTBISOTYP = filter this with 'QUERY' or whatever your need is.
*BI Application Object 0TCTBISBOBJ, ( this will give you the name of the queries)
In key figures choose, Count for BI Appl. (0TCTWTCOUNT).
(number for query run)
Create a condition , for top 20.
Hope this helps.
Derya

What are the differences between iphoto ios5 and iphoto ios6?

what are the differences between iphoto ios5 and iphoto ios6?

There is no difference unless you update iPhoto.
The iPhoto.app was updated and now version 1.1 is available. This version includes the ability to create Shared Photo Streams if you have iOS 6.
-Doug

What are the advantages of using CACHE and NOCACHE Hint

What are the advantages of using CACHE and NOCACHE Hint & difference of them.I saw one of oracle.sql script have CACHE & oracle rac script include NOCACHE .Why is that

924250 wrote:
In a SOA product include db scripts,when we install the product we want to execute the db script to create sequence both oracle RAC & Oracle db
Oracle DB
CREATE SEQUENCE REG_LOG_SEQUENCE START WITH 1 INCREMENT BY 1 NOCACHE
Oracle RAC DB
CREATE SEQUENCE REG_LOG_SEQUENCE START WITH 1 INCREMENT BY 1 CACHE 20 ORDERas sb mentioned, this has nothing to do with oracle hints.
you'll want to search the documentation about sequences.

What are the configuration need between R3 and XI when we use RFC sync adap

hi,
What are the configuration need between R3 and XI when we use RFC sync adapter.
Regards
siva.

if its the sender adapter ref:
RFC adapter
Sender- /people/michal.krawczyk2/blog/2005/03/29/configuring-the-sender-rfc-adapter--step-by-step
Receiver;
http://help.sap.com/saphelp_nw04/helpdata/en/c8/e80440a832e369e10000000a155106/content.htm
Also;
trouble shooting rfc/soap -
/people/shabarish.vijayakumar/blog/2008/01/08/troubleshooting--rfc-and-soap-scenarios-updated-on-20042009

What is procedure for creating new vendor and material master data in ABAP

What is procedure for creating new vendor and material master data in ABAP .

see below code which is used for creation of vendor master as well as extension...
*& Report ZFC_VENDOR_CREATE *
REPORT ZFC_VENDOR_CREATE LINE-SIZE 100
 NO STANDARD PAGE HEADING
 MESSAGE-ID ZZ.
 TABLES
TABLES : SSCRFIELDS. " Fields on selection screens
 CONSTANTS
DATA : C_SPLIT TYPE C VALUE '#'. " Used for Has Separator in GUI_UPLAOD
 TYPES
Int'table to hold Vendor Master Data
TYPES : BEGIN OF TY_VENDOR_MASTER,
 FLAG TYPE C, " Update Flag
 LIFNR TYPE LIFNR, " Vendor Number
 BUKRS TYPE BUKRS, " Company Code
 KTOKK TYPE KTOKK, " Account Group
 ANRED TYPE ANRED, " Title
 NAME1 TYPE NAME1_GP, " Name1
 NAME2 TYPE NAME2_GP, " Name2
 SORTL TYPE SORTL, " Search Term 1
 SORT2 TYPE AD_SORT2UL, " Search Term 2
 STRAS TYPE STRAS_GP, " Street
 PSTLZ TYPE PSTLZ, " Postal Code
 ORT01 TYPE ORT01_GP, " City
 REGIO TYPE REGIO, " Region
 LAND1 TYPE LAND1_GP, " Country
 SPRAS TYPE SPRAS, " Language
 VBUND TYPE RASSC, " Trading Partner
 BANKS TYPE BANKS, " Country
 BANKL TYPE BANKK, " Bank Key
 BANKN TYPE BANKN, " Bank Account
 BKONT TYPE BKONT, " Bank Control Key
 BANKA TYPE BANKA, " Name of Bank
 AKONT TYPE AKONT, " Reconciliation Account
 FDGRV TYPE FDGRV, " Cash Management Group
 ZTERM TYPE DZTERM, " Payment Terms
 REPRF TYPE REPRF, " Check Double Invoice
 ZWELS TYPE DZWELS, " Payment Methods
 XPORE TYPE XPORE, " Pay all items separately
 END OF TY_VENDOR_MASTER,
Int'table to hold Vendor Extend Data
 BEGIN OF TY_VENDOR_EXTEND,
 FLAG TYPE C, " Update Flag
 LIFNR TYPE LIFNR, " Vendor Number
 BUKRS TYPE BUKRS, " Company Code
 KTOKK TYPE KTOKK, " Account Group
 REF_LIFNR TYPE LIFNR, " Reference Vendor Number
 REF_BUKRS TYPE BUKRS, " Reference Company Code
 AKONT TYPE AKONT, " Reconciliation Account
 FDGRV TYPE FDGRV, " Cash Management Group
 ZTERM TYPE DZTERM, " Payment Terms
 REPRF TYPE REPRF, " Check Double Invoice
 ZWELS TYPE DZWELS, " Payment Methods
 XPORE TYPE XPORE, " Pay all items separately
 END OF TY_VENDOR_EXTEND,
Int'table to hold Error Records Data
 BEGIN OF TY_ERROR,
 MSG(200) TYPE C, " To hold Message
 LIFNR TYPE LIFNR, " Vendor Number
 BUKRS TYPE BUKRS, " Company Code
 END OF TY_ERROR.
 DATA (Simple Fields)
DATA : W_COUNT TYPE I, " Variable to hold count of Records
 W_SUCC_REC TYPE I, " No. of Success Records
 W_SUCC_REC1 TYPE I, " No. of Updated Records
 W_ERR_REC TYPE I, " No. of Error Records
 w_noupdate_rec type i. " No. of Records not Changed
 INTERNAL TABLES
Int'table to hold uploaded data from File
DATA : IT_VENDOR_MASTER TYPE STANDARD TABLE OF TY_VENDOR_MASTER,
 WA_IT_VENDOR_MASTER TYPE TY_VENDOR_MASTER,
 IT_VENDOR_EXTEND TYPE STANDARD TABLE OF TY_VENDOR_EXTEND,
 WA_IT_VENDOR_EXTEND TYPE TY_VENDOR_EXTEND,
 WA_IT_BDCDATA TYPE BDCDATA,
 IT_BDCDATA TYPE STANDARD TABLE OF BDCDATA,
 WA_IT_MESSTAB TYPE BDCMSGCOLL,
 IT_MESSTAB TYPE STANDARD TABLE OF BDCMSGCOLL,
 IT_ERROR TYPE STANDARD TABLE OF TY_ERROR,
 WA_IT_ERROR TYPE TY_ERROR,
 it_error_fk01 type standard table of ty_error,
 wa_it_error_fk01 type ty_error,
 it_error_fk02 type standard table of ty_error,
 wa_it_error_fk02 type ty_error,
 it_succ_rec1 type standard table of ty_error,
 wa_it_succ_rec1 type ty_error,
 it_noupdate type standard table of ty_error,
 wa_it_noupdate type ty_error.
 FLAGS
DATA : FL_FLAG1 TYPE C, " Flag to check error upload file
 FL_FLAG2 TYPE C, " Flag to hold value
 FL_FLAG3 TYPE C, " Flag to hold value
 FL_FLAG4 TYPE C. " Flag to hold value
 SELECTION-SCREEN
SELECTION-SCREEN BEGIN OF BLOCK B1 WITH FRAME TITLE TEXT-001.
SELECTION-SCREEN : BEGIN OF LINE,
 COMMENT 1(30) TEXT-001,
 POSITION POS_LOW.
PARAMETERS : P_FILE(128) DEFAULT 'C:\UPLOAD.TXT' OBLIGATORY.
SELECTION-SCREEN : END OF LINE.
SELECTION-SCREEN : BEGIN OF LINE,
 COMMENT 1(30) TEXT-002,
 POSITION POS_LOW.
PARAMETERS : P_VENMAS RADIOBUTTON GROUP R1 DEFAULT 'X'.
SELECTION-SCREEN : END OF LINE.
SELECTION-SCREEN : BEGIN OF LINE,
 COMMENT 1(30) TEXT-003,
 POSITION POS_LOW.
PARAMETERS : P_VENEXT RADIOBUTTON GROUP R1.
SELECTION-SCREEN : END OF LINE.
SELECTION-SCREEN SKIP 2.
SELECTION-SCREEN : BEGIN OF LINE,
 COMMENT 1(30) TEXT-004,
 POSITION POS_LOW.
PARAMETERS : P_MODE(1) DEFAULT 'N'.
SELECTION-SCREEN : END OF LINE.
SELECTION-SCREEN : BEGIN OF LINE,
 COMMENT 1(30) TEXT-005,
 POSITION POS_LOW.
PARAMETERS : P_GROUP(12) DEFAULT 'ZFC_VENDOR_C' OBLIGATORY.
SELECTION-SCREEN : END OF LINE.
SELECTION-SCREEN : BEGIN OF LINE,
 COMMENT 1(30) TEXT-016,
 POSITION POS_LOW.
PARAMETERS : P_GROUP1(12) DEFAULT 'ZFC_VENDOR_U' OBLIGATORY.
SELECTION-SCREEN : END OF LINE.
SELECTION-SCREEN END OF BLOCK B1.
 AT SELECTION-SCREEN ON
AT SELECTION-SCREEN ON VALUE-REQUEST FOR P_FILE.
Form to get file path for upload of data
PERFORM GET_FILE_PATH.
AT SELECTION-SCREEN ON BLOCK B1.
Form to Validate data specified on Selection Screen
CHECK SSCRFIELDS-UCOMM EQ 'ONLI'.
PERFORM VALIDATE_DATA.
 START - OF - SELECTION
START-OF-SELECTION.
IF P_VENMAS = 'X'.
Form to upload data from Presentation Server for Vendor Master
 PERFORM UPLOAD_DATA TABLES IT_VENDOR_MASTER.
 IF FL_FLAG1 NE 'X'.
 SORT IT_VENDOR_MASTER BY LIFNR BUKRS KTOKK.
 DELETE IT_VENDOR_MASTER WHERE LIFNR = ' '
 AND BUKRS = ' '
 AND KTOKK = ' '.
Form to process data for Vendor Master
 PERFORM INSERT_VENDOR_MASTER_DATA.
 ENDIF.
ELSEIF P_VENEXT = 'X'.
Form to upload data from Presentation Server for Vendor Extend
 PERFORM UPLOAD_DATA TABLES IT_VENDOR_EXTEND.
 IF FL_FLAG1 NE 'X'.
 SORT IT_VENDOR_EXTEND BY LIFNR BUKRS KTOKK.
 DELETE IT_VENDOR_EXTEND WHERE LIFNR = ' '
 AND BUKRS = ' '
 AND KTOKK = ' '.
Form to process data for Vendor Master
 PERFORM CHK_AND_INS_VENDOR_EXTEND_DATA.
 ENDIF.
ENDIF.
 END - OF - SELECTION
END-OF-SELECTION.
IF FL_FLAG1 NE 'X'.
 FORMAT COLOR 7.
 WRITE:/2 TEXT-O01. " Total Number of records read :
 FORMAT COLOR OFF.
 WRITE:40 W_COUNT.
 FORMAT COLOR 7.
 WRITE:/2 TEXT-O02. " Total Number of Success records :
 FORMAT COLOR OFF.
 WRITE:40 W_SUCC_REC.
 FORMAT COLOR 7.
 WRITE:/2 TEXT-O07. " Total Number of Updated records :
 FORMAT COLOR OFF.
 WRITE:40 W_SUCC_REC1.
 FORMAT COLOR 7.
 WRITE:/2 TEXT-O08. " Total Number of Unchanged records :
 FORMAT COLOR OFF.
 WRITE:40 W_noupdate_REC.
 FORMAT COLOR 7.
 WRITE:/2 TEXT-O03. " Total Number of Error records :
 FORMAT COLOR OFF.
 WRITE:40 W_ERR_REC.
 if not it_succ_rec1 is initial.
 skip 1.
 perform display_changed_report.
 endif.
 if not it_noupdate is initial.
 skip 1.
 perform display_nochange_report.
 endif.
 IF NOT IT_ERROR IS INITIAL.
 SKIP 3.
Form to display error data
 PERFORM DISPLAY_ERROR_REPORT.
 ENDIF.
 IF FL_FLAG2 = 'X'.
 SKIP 2.
 FORMAT COLOR 4.
 WRITE:/2 TEXT-O04. " BDC Session Name for Creation (FK01) :
 FORMAT COLOR OFF.
 WRITE:40 P_GROUP.
 perform display_error_report_fk01.
 ENDIF.
 IF FL_FLAG3 = 'X'.
 SKIP 2.
 FORMAT COLOR 4.
 WRITE:/2 TEXT-O09. " BDC Session Name for Updation (FK02) :
 FORMAT COLOR OFF.
 WRITE:40 P_GROUP1.
 perform display_error_report_fk02.
 ENDIF.
ENDIF.
*& Form GET_FILE_PATH
This form is used to get the specified path for uploading of data from
flat file with the help of F4 function key
FORM GET_FILE_PATH .
CALL FUNCTION 'F4_FILENAME'
 EXPORTING
 PROGRAM_NAME = SYST-CPROG
 DYNPRO_NUMBER = SYST-DYNNR
 FIELD_NAME = ' '
 IMPORTING
 FILE_NAME = P_FILE.
ENDFORM. " GET_FILE_PATH
*& Form VALIDATE_DATA
This form is used to validate the data given by user on the Selection
Screen and the appropriate message is been displayed when an wrong
entry is inputted
FORM VALIDATE_DATA .
IF SY-BATCH EQ 'X'.
 CLEAR SSCRFIELDS-UCOMM.
 MESSAGE E001(ZZ) WITH TEXT-011.
 " Excel file not to be used in Batch Mode
ENDIF.
IF P_MODE NE 'A' AND P_MODE NE 'N' AND P_MODE NE 'E'.
 MESSAGE E001(ZZ) WITH TEXT-012.
 " Session Mode should be either A or N or E
ENDIF.
ENDFORM. " VALIDATE_DATA
*& Form UPLOAD_DATA
This form is used to upload data from Presentation Server for either
Vendor Master or Vendor Extend
FORM UPLOAD_DATA TABLES P_IT_VENDOR.
DATA : L_FILENAME TYPE STRING,
 L_FILETYPE TYPE CHAR10 VALUE 'ASC',
 L_HEADER_LENGTH TYPE I VALUE 0,
 L_READ_BY_LINE TYPE CHAR01 VALUE 'X'.
MOVE P_FILE TO L_FILENAME.
CALL FUNCTION 'GUI_UPLOAD'
 EXPORTING
 FILENAME = L_FILENAME
 FILETYPE = L_FILETYPE
 HEADER_LENGTH = L_HEADER_LENGTH
 READ_BY_LINE = L_READ_BY_LINE
 HAS_FIELD_SEPARATOR = C_SPLIT
 TABLES
 DATA_TAB = P_IT_VENDOR
 EXCEPTIONS
 FILE_OPEN_ERROR = 1
 FILE_READ_ERROR = 2
 NO_BATCH = 3
 GUI_REFUSE_FILETRANSFER = 4
 INVALID_TYPE = 5
 NO_AUTHORITY = 6
 UNKNOWN_ERROR = 7
 BAD_DATA_FORMAT = 8
 HEADER_NOT_ALLOWED = 9
 SEPARATOR_NOT_ALLOWED = 10
 HEADER_TOO_LONG = 11
 UNKNOWN_DP_ERROR = 12
 ACCESS_DENIED = 13
 DP_OUT_OF_MEMORY = 14
 DISK_FULL = 15
 DP_TIMEOUT = 16
 OTHERS = 17.
IF SY-SUBRC <> 0.
 MESSAGE I001(ZZ) WITH TEXT-006 L_FILENAME.
MESSAGE ID SY-MSGID TYPE 'I' NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
 FL_FLAG1 = 'X'.
ELSEIF P_IT_VENDOR[] IS INITIAL.
 MESSAGE I001(ZZ) WITH TEXT-014. " Uploaded File contains no data
 FL_FLAG1 = 'X'.
ENDIF.
ENDFORM. " UPLOAD_DATA
*& Form INSERT_VENDOR_MASTER_DATA
This form is used to process BDC data for Vendor Master
FORM INSERT_VENDOR_MASTER_DATA .
DATA : L_LIFNR TYPE LIFNR.
CLEAR : L_LIFNR.
sort it_vendor_master by flag.
LOOP AT IT_VENDOR_MASTER INTO WA_IT_VENDOR_MASTER.
 W_COUNT = W_COUNT + 1.
 CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
 EXPORTING
 INPUT = WA_IT_VENDOR_MASTER-LIFNR
 IMPORTING
 OUTPUT = WA_IT_VENDOR_MASTER-LIFNR.
 if wa_it_vendor_master-flag = 'A'.
 SELECT SINGLE LIFNR
 FROM LFB1
 INTO L_LIFNR
 WHERE LIFNR = WA_IT_VENDOR_MASTER-LIFNR
 AND BUKRS = WA_IT_VENDOR_MASTER-BUKRS.
 IF SY-SUBRC EQ 0.
 WA_IT_ERROR-LIFNR = WA_IT_VENDOR_MASTER-LIFNR.
 WA_IT_ERROR-BUKRS = WA_IT_VENDOR_MASTER-BUKRS.
 WA_IT_ERROR-MSG = TEXT-015.
 APPEND WA_IT_ERROR TO IT_ERROR.
 W_ERR_REC = W_ERR_REC + 1.
 CLEAR : WA_IT_ERROR, L_LIFNR.
 ELSE.
 REFRESH IT_BDCDATA.
 CLEAR IT_BDCDATA.
 PERFORM POPULATE_BDC_DATA_VEN_MASTER.
 PERFORM CALL_TRANSACTION.
 ENDIF.
 CLEAR : WA_IT_VENDOR_MASTER.
 elseif wa_it_vendor_master-flag = 'C'.
 IF FL_FLAG2 = 'X' and fl_flag4 ne 'X'.
 PERFORM CLOSE_BDC_SESSION.
 fl_flag4 = 'X'.
 ENDIF.
 REFRESH IT_BDCDATA.
 CLEAR IT_BDCDATA.
 PERFORM POPULATE_BDC_DATA_VEN_MASTER.
 PERFORM CALL_TRANSACTION_FK02.
 CLEAR : WA_IT_VENDOR_MASTER.
 elseif wa_it_vendor_master-flag = 'N'.
 WA_IT_noupdate-LIFNR = WA_IT_VENDOR_MASTER-LIFNR.
 WA_IT_noupdate-BUKRS = WA_IT_VENDOR_MASTER-BUKRS.
 WA_IT_noupdate-MSG = TEXT-018.
 APPEND WA_IT_noupdate TO IT_noupdate.
 W_noupdate_REC = W_noupdate_REC + 1.
 CLEAR : WA_IT_noupdate, WA_IT_VENDOR_MASTER.
 endif.
ENDLOOP.
IF FL_FLAG3 = 'X'.
 PERFORM CLOSE_BDC_SESSION.
ENDIF.
ENDFORM. " INSERT_VENDOR_MASTER_DATA
*& Form POPULATE_BDC_DATA_VEN_MASTER
This form is used to populate BDC data of Vendor Master
FORM POPULATE_BDC_DATA_VEN_MASTER .
CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
 EXPORTING
 INPUT = WA_IT_VENDOR_MASTER-ZTERM
 IMPORTING
 OUTPUT = WA_IT_VENDOR_MASTER-ZTERM.
IF WA_IT_VENDOR_MASTER-REPRF = 'Y'.
 WA_IT_VENDOR_MASTER-REPRF = 'X'.
ENDIF.
IF WA_IT_VENDOR_MASTER-XPORE = 'Y'.
 WA_IT_VENDOR_MASTER-XPORE = 'X'.
ENDIF.
if wa_it_vendor_master-flag = 'A'.
PERFORM :BDC_DYNPRO USING 'SAPMF02K' '0105',
 BDC_FIELD USING 'RF02K-LIFNR' WA_IT_VENDOR_MASTER-LIFNR,
 BDC_FIELD USING 'RF02K-BUKRS' WA_IT_VENDOR_MASTER-BUKRS,
 BDC_FIELD USING 'RF02K-KTOKK' WA_IT_VENDOR_MASTER-KTOKK,
 BDC_FIELD USING 'BDC_OKCODE' '/00'.
elseif wa_it_vendor_master-flag = 'C'.
PERFORM :BDC_DYNPRO USING 'SAPMF02K' '0106',
 BDC_FIELD USING 'RF02K-LIFNR' WA_IT_VENDOR_MASTER-LIFNR,
 BDC_FIELD USING 'RF02K-BUKRS' WA_IT_VENDOR_MASTER-BUKRS,
 BDC_FIELD USING 'BDC_OKCODE' '=MALL',
 BDC_DYNPRO USING 'SAPMF02K' '0106',
 BDC_FIELD USING 'RF02K-D0110' 'X',
 BDC_FIELD USING 'RF02K-D0120' 'X',
 BDC_FIELD USING 'RF02K-D0130' 'X',
 BDC_FIELD USING 'RF02K-D0210' 'X',
 BDC_FIELD USING 'RF02K-D0215' 'X',
 BDC_FIELD USING 'RF02K-D0220' 'X',
 BDC_FIELD USING 'BDC_OKCODE' '/00'.
endif.
perform :BDC_DYNPRO USING 'SAPMF02K' '0110',
 BDC_FIELD USING 'LFA1-ANRED' WA_IT_VENDOR_MASTER-ANRED,
 BDC_FIELD USING 'LFA1-NAME1' WA_IT_VENDOR_MASTER-NAME1,
 BDC_FIELD USING 'LFA1-NAME2' WA_IT_VENDOR_MASTER-NAME2,
 BDC_FIELD USING 'LFA1-SORTL' WA_IT_VENDOR_MASTER-SORTL,
 BDC_FIELD USING 'LFA1-STRAS' WA_IT_VENDOR_MASTER-STRAS,
 BDC_FIELD USING 'LFA1-ORT01' WA_IT_VENDOR_MASTER-ORT01,
 BDC_FIELD USING 'LFA1-PSTLZ' WA_IT_VENDOR_MASTER-PSTLZ,
 BDC_FIELD USING 'LFA1-LAND1' WA_IT_VENDOR_MASTER-LAND1,
 BDC_FIELD USING 'LFA1-REGIO' WA_IT_VENDOR_MASTER-REGIO,
 BDC_FIELD USING 'LFA1-SPRAS' WA_IT_VENDOR_MASTER-SPRAS,
 BDC_FIELD USING 'BDC_OKCODE' '/00',
 BDC_DYNPRO USING 'SAPMF02K' '0120',
 BDC_FIELD USING 'LFA1-VBUND' WA_IT_VENDOR_MASTER-VBUND,
 BDC_FIELD USING 'BDC_OKCODE' '/00',
 BDC_DYNPRO USING 'SAPMF02K' '0130',
 BDC_FIELD USING 'LFBK-BANKS(01)' WA_IT_VENDOR_MASTER-BANKS,
 BDC_FIELD USING 'LFBK-BANKL(01)' WA_IT_VENDOR_MASTER-BANKL,
 BDC_FIELD USING 'LFBK-BANKN(01)' WA_IT_VENDOR_MASTER-BANKN,
 BDC_FIELD USING 'BDC_OKCODE' '=BANK',
 BDC_DYNPRO USING 'SAPLBANK' '0100',
 BDC_FIELD USING 'BNKA-BANKA' WA_IT_VENDOR_MASTER-BANKA,
 BDC_FIELD USING 'BDC_OKCODE' '=ENTR',
 BDC_DYNPRO USING 'SAPMF02K' '0130',
 BDC_FIELD USING 'BDC_OKCODE' '=ENTR',
 BDC_DYNPRO USING 'SAPMF02K' '0210',
 BDC_FIELD USING 'LFB1-AKONT' WA_IT_VENDOR_MASTER-AKONT,
 BDC_FIELD USING 'LFB1-FDGRV' WA_IT_VENDOR_MASTER-FDGRV,
 BDC_FIELD USING 'BDC_OKCODE' '=/00',
 BDC_DYNPRO USING 'SAPMF02K' '0215',
 BDC_FIELD USING 'LFB1-ZTERM' WA_IT_VENDOR_MASTER-ZTERM,
 BDC_FIELD USING 'LFB1-REPRF' WA_IT_VENDOR_MASTER-REPRF,
 BDC_FIELD USING 'LFB1-ZWELS' WA_IT_VENDOR_MASTER-ZWELS,
 BDC_FIELD USING 'LFB1-XPORE' WA_IT_VENDOR_MASTER-XPORE,
 BDC_FIELD USING 'BDC_OKCODE' '=UPDA'.
ENDFORM. " POPULATE_BDC_DATA_VEN_MASTER
*& Form BDC_DYNPRO
This form is used to move data to BDCDATA int'table
FORM BDC_DYNPRO USING PROGRAM TYPE BDC_PROG
 DYNPRO TYPE BDC_DYNR.
CLEAR WA_IT_BDCDATA.
WA_IT_BDCDATA-PROGRAM = PROGRAM.
WA_IT_BDCDATA-DYNPRO = DYNPRO.
WA_IT_BDCDATA-DYNBEGIN = 'X'.
APPEND WA_IT_BDCDATA TO IT_BDCDATA.
ENDFORM. " BDC_DYNPRO
*& Form BDC_FIELD
This form is used to move data to BDCDATA int'table
FORM BDC_FIELD USING FNAM TYPE ANY
 FVAL TYPE ANY.
CLEAR WA_IT_BDCDATA.
WA_IT_BDCDATA-FNAM = FNAM.
WA_IT_BDCDATA-FVAL = FVAL.
APPEND WA_IT_BDCDATA TO IT_BDCDATA.
ENDFORM. " BDC_FIELD
*& Form CALL_TRANSACTION
This form is used to Call FK01 for processing of data either for
Vendor Master or Vendor Extend. The error records are inserted to
Session which can be processed using SM35
FORM CALL_TRANSACTION .
DATA : L_OPTION TYPE CTU_PARAMS,
 L_SUBRC TYPE SYSUBRC.
REFRESH IT_MESSTAB.
CLEAR IT_MESSTAB.
L_OPTION-DEFSIZE = 'X'.
L_OPTION-DISMODE = P_MODE.
L_OPTION-UPDMODE = 'S'.
CALL TRANSACTION 'FK01'
 USING IT_BDCDATA
 MESSAGES INTO IT_MESSTAB
 OPTIONS FROM L_OPTION.
L_SUBRC = SY-SUBRC.
IF L_SUBRC = 0.
 W_SUCC_REC = W_SUCC_REC + 1.
ELSE.
 IF FL_FLAG2 NE 'X'.
 PERFORM OPEN_BDC_SESSION.
 FL_FLAG2 = 'X'.
 ENDIF.
 PERFORM BDC_INSERT.
 W_ERR_REC = W_ERR_REC + 1.
 PERFORM ERROR_RECORD_DATA.
ENDIF.
ENDFORM. " CALL_TRANSACTION
*& Form OPEN_BDC_SESSION
Form used to open session for Error out Records
FORM OPEN_BDC_SESSION .
DATA : L_USERID TYPE APQ_MAPN, " Variable to hold user-id
 L_GROUP TYPE APQ_GRPN. " Variable to hold value
MOVE P_GROUP TO L_GROUP.
MOVE SY-UNAME TO L_USERID.
CALL FUNCTION 'BDC_OPEN_GROUP'
 EXPORTING
 CLIENT = SY-MANDT
 GROUP = L_GROUP
 KEEP = SPACE
 USER = L_USERID
 EXCEPTIONS
 CLIENT_INVALID = 1
 DESTINATION_INVALID = 2
 GROUP_INVALID = 3
 GROUP_IS_LOCKED = 4
 HOLDDATE_INVALID = 5
 INTERNAL_ERROR = 6
 QUEUE_ERROR = 7
 RUNNING = 8
 SYSTEM_LOCK_ERROR = 9
 USER_INVALID = 10
 OTHERS = 11.
IF SY-SUBRC <> 0.
 WRITE:/ TEXT-008. " Unable to open BDC Session
ENDIF.
ENDFORM. " OPEN_BDC_SESSION
*& Form BDC_INSERT
This form is used to insert error records to a Session method
FORM BDC_INSERT .
CALL FUNCTION 'BDC_INSERT'
 EXPORTING
 TCODE = 'FK01'
 TABLES
 DYNPROTAB = IT_BDCDATA
 EXCEPTIONS
 INTERNAL_ERROR = 1
 NOT_OPEN = 2
 QUEUE_ERROR = 3
 TCODE_INVALID = 4
 PRINTING_INVALID = 5
 POSTING_INVALID = 6
 OTHERS = 7.
IF SY-SUBRC <> 0.
 WRITE:/ TEXT-009. " Unable to Insert Data to BDC Session
ENDIF.
ENDFORM. " BDC_INSERT
*& Form ERROR_RECORD_DATA
This form is used to process the messages for the error records which
will be displayed on the output report
FORM ERROR_RECORD_DATA .
DATA : L_LINES TYPE I,
 L_MSG(200) TYPE C.
DESCRIBE TABLE IT_MESSTAB LINES L_LINES.
READ TABLE IT_MESSTAB INTO WA_IT_MESSTAB INDEX L_LINES.
IF SY-SUBRC = 0.
 CLEAR L_MSG.
 CALL FUNCTION 'FORMAT_MESSAGE'
 EXPORTING
 ID = WA_IT_MESSTAB-MSGID
 LANG = SY-LANGU
 NO = WA_IT_MESSTAB-MSGNR
 V1 = WA_IT_MESSTAB-MSGV1
 V2 = WA_IT_MESSTAB-MSGV2
 V3 = WA_IT_MESSTAB-MSGV3
 V4 = WA_IT_MESSTAB-MSGV4
 IMPORTING
 MSG = L_MSG
 EXCEPTIONS
 NOT_FOUND = 1
 OTHERS = 2.
 IF SY-SUBRC = 0.
 WA_IT_ERROR_fk01-MSG = L_MSG.
 ENDIF.
 IF P_VENMAS = 'X'.
 WA_IT_ERROR_fk01-LIFNR = WA_IT_VENDOR_MASTER-LIFNR.
 WA_IT_ERROR_fk01-BUKRS = WA_IT_VENDOR_MASTER-BUKRS.
 ELSEIF P_VENEXT = 'X'.
 WA_IT_ERROR_fk01-LIFNR = WA_IT_VENDOR_EXTEND-LIFNR.
 WA_IT_ERROR_fk01-BUKRS = WA_IT_VENDOR_EXTEND-BUKRS.
 ENDIF.
 APPEND WA_IT_ERROR_fk01 TO IT_ERROR_fk01.
 CLEAR WA_IT_ERROR_fk01.
ENDIF.
ENDFORM. " ERROR_RECORD_DATA
*& Form CLOSE_BDC_SESSION
Form used to close session of the Error Records
FORM CLOSE_BDC_SESSION .
CALL FUNCTION 'BDC_CLOSE_GROUP'
 EXCEPTIONS
 NOT_OPEN = 1
 QUEUE_ERROR = 2
 OTHERS = 3.
IF SY-SUBRC <> 0.
 WRITE:/ TEXT-010. " Unable to Close BDC Session
ENDIF.
ENDFORM. " CLOSE_BDC_SESSION
*& Form CHK_AND_INS_VENDOR_EXTEND_DATA
This form is used to process BDC data for Vendor Extend
FORM CHK_AND_INS_VENDOR_EXTEND_DATA .
DATA : L_LIFNR TYPE LIFNR.
CLEAR : L_LIFNR, fl_flag4.
sort it_vendor_extend by flag.
LOOP AT IT_VENDOR_EXTEND INTO WA_IT_VENDOR_EXTEND.
 W_COUNT = W_COUNT + 1.
 CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
 EXPORTING
 INPUT = WA_IT_VENDOR_EXTEND-REF_LIFNR
 IMPORTING
 OUTPUT = WA_IT_VENDOR_EXTEND-REF_LIFNR.
 if wa_it_vendor_extend-flag = 'A'.
 SELECT SINGLE LIFNR
 FROM LFB1
 INTO L_LIFNR
 WHERE LIFNR = WA_IT_VENDOR_EXTEND-REF_LIFNR
 AND BUKRS = WA_IT_VENDOR_EXTEND-REF_BUKRS.
 IF SY-SUBRC NE 0.
 WA_IT_ERROR-LIFNR = WA_IT_VENDOR_EXTEND-REF_LIFNR.
 WA_IT_ERROR-BUKRS = WA_IT_VENDOR_EXTEND-REF_BUKRS.
 WA_IT_ERROR-MSG = TEXT-007.
 APPEND WA_IT_ERROR TO IT_ERROR.
 W_ERR_REC = W_ERR_REC + 1.
 CLEAR : WA_IT_ERROR, L_LIFNR.
 ELSE.
 CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
 EXPORTING
 INPUT = WA_IT_VENDOR_EXTEND-LIFNR
 IMPORTING
 OUTPUT = WA_IT_VENDOR_EXTEND-LIFNR.
 SELECT SINGLE LIFNR
 FROM LFB1
 INTO L_LIFNR
 WHERE LIFNR = WA_IT_VENDOR_EXTEND-LIFNR
 AND BUKRS = WA_IT_VENDOR_EXTEND-BUKRS.
 IF SY-SUBRC EQ 0.
 WA_IT_ERROR-LIFNR = WA_IT_VENDOR_EXTEND-LIFNR.
 WA_IT_ERROR-BUKRS = WA_IT_VENDOR_EXTEND-BUKRS.
 WA_IT_ERROR-MSG = TEXT-015.
 APPEND WA_IT_ERROR TO IT_ERROR.
 W_ERR_REC = W_ERR_REC + 1.
 CLEAR : WA_IT_ERROR, L_LIFNR.
 ELSE.
 REFRESH IT_BDCDATA.
 CLEAR IT_BDCDATA.
 PERFORM POPULATE_BDC_DATA_VEN_EXTEND.
 PERFORM CALL_TRANSACTION.
 ENDIF.
 ENDIF.
 CLEAR : WA_IT_VENDOR_EXTEND.
 elseif wa_it_vendor_extend-flag = 'C'.
 IF FL_FLAG2 = 'X' and fl_flag4 ne 'X'.
 PERFORM CLOSE_BDC_SESSION.
 fl_flag4 = 'X'.
 ENDIF.
 REFRESH IT_BDCDATA.
 CLEAR IT_BDCDATA.
 PERFORM POPULATE_BDC_DATA_VEN_extend.
 PERFORM CALL_TRANSACTION_FK02.
 CLEAR : WA_IT_VENDOR_EXTEND.
 elseif wa_it_vendor_extend-flag = 'N'.
 WA_IT_noupdate-LIFNR = WA_IT_VENDOR_extend-LIFNR.
 WA_IT_noupdate-BUKRS = WA_IT_VENDOR_extend-BUKRS.
 WA_IT_noupdate-MSG = TEXT-019.
 APPEND WA_IT_noupdate TO IT_noupdate.
 W_noupdate_REC = W_noupdate_REC + 1.
 CLEAR : WA_IT_noupdate, WA_IT_VENDOR_EXTEND.
 endif.
ENDLOOP.
IF FL_FLAG2 = 'X'.
 PERFORM CLOSE_BDC_SESSION.
ENDIF.
if fl_flag3 = 'X'.
 PERFORM CLOSE_BDC_SESSION.
ENDIF.
ENDFORM. " CHK_AND_INS_VENDOR_EXTEND_DATA
*& Form POPULATE_BDC_DATA_VEN_EXTEND
This form is used to populate BDC data of Vendor Extend
FORM POPULATE_BDC_DATA_VEN_EXTEND .
CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
 EXPORTING
 INPUT = WA_IT_VENDOR_EXTEND-ZTERM
 IMPORTING
 OUTPUT = WA_IT_VENDOR_EXTEND-ZTERM.
IF WA_IT_VENDOR_EXTEND-REPRF = 'Y'.
 WA_IT_VENDOR_EXTEND-REPRF = 'X'.
ENDIF.
IF WA_IT_VENDOR_extend-XPORE = 'Y'.
 WA_IT_VENDOR_extend-XPORE = 'X'.
ENDIF.
if wa_it_vendor_extend-flag = 'A'.
PERFORM :BDC_DYNPRO USING 'SAPMF02K' '0105',
 BDC_FIELD USING 'RF02K-LIFNR' WA_IT_VENDOR_EXTEND-LIFNR,
 BDC_FIELD USING 'RF02K-BUKRS' WA_IT_VENDOR_EXTEND-BUKRS,
 BDC_FIELD USING 'RF02K-KTOKK' WA_IT_VENDOR_EXTEND-KTOKK,
 BDC_FIELD USING 'RF02K-REF_LIFNR'
 WA_IT_VENDOR_EXTEND-REF_LIFNR,
 BDC_FIELD USING 'RF02K-REF_BUKRS'
 WA_IT_VENDOR_EXTEND-REF_BUKRS,
 BDC_FIELD USING 'BDC_OKCODE' '/00'.
elseif wa_it_vendor_extend-flag = 'C'.
PERFORM :BDC_DYNPRO USING 'SAPMF02K' '0106',
 BDC_FIELD USING 'RF02K-LIFNR' WA_IT_VENDOR_extend-LIFNR,
 BDC_FIELD USING 'RF02K-BUKRS' WA_IT_VENDOR_extend-BUKRS,
 BDC_FIELD USING 'RF02K-D0210' 'X',
 BDC_FIELD USING 'RF02K-D0215' 'X',
 BDC_FIELD USING 'BDC_OKCODE' '/00'.
endif.
perform :BDC_DYNPRO USING 'SAPMF02K' '0210',
 BDC_FIELD USING 'LFB1-AKONT' WA_IT_VENDOR_EXTEND-AKONT,
 BDC_FIELD USING 'LFB1-FDGRV' WA_IT_VENDOR_EXTEND-FDGRV,
 BDC_FIELD USING 'BDC_OKCODE' '=/00',
 BDC_DYNPRO USING 'SAPMF02K' '0215',
 BDC_FIELD USING 'LFB1-ZTERM' WA_IT_VENDOR_EXTEND-ZTERM,
 BDC_FIELD USING 'LFB1-REPRF' WA_IT_VENDOR_EXTEND-REPRF,
 BDC_FIELD USING 'LFB1-ZWELS' WA_IT_VENDOR_EXTEND-ZWELS,
 BDC_FIELD USING 'LFB1-XPORE' WA_IT_VENDOR_extend-XPORE,
 BDC_FIELD USING 'BDC_OKCODE' '=UPDA'.
ENDFORM. " POPULATE_BDC_DATA_VEN_EXTEND
*& Form DISPLAY_ERROR_REPORT
This form is used to display the error records on the output screen
FORM DISPLAY_ERROR_REPORT .
IF P_VENMAS = 'X'.
 WRITE:/ TEXT-O05. " Error List for Vendor Master
ELSEIF P_VENEXT = 'X'.
 WRITE:/ TEXT-O06. " Error List for Vendor Master Extended
ENDIF.
WRITE:/ SY-ULINE(100).
FORMAT COLOR 1.
WRITE:/1 SY-VLINE,
 2 TEXT-H01, " Vendor Number
 17 SY-VLINE,
 18 TEXT-H02, " Company Code
 31 SY-VLINE,
 32 TEXT-H03, " Error Message
 100 SY-VLINE.
FORMAT COLOR OFF.
WRITE:/ SY-ULINE(100).
LOOP AT IT_ERROR INTO WA_IT_ERROR.
 FORMAT COLOR 2.
 WRITE:/1 SY-VLINE,
 2 WA_IT_ERROR-LIFNR,
 17 SY-VLINE,
 18 WA_IT_ERROR-BUKRS,
 31 SY-VLINE,
 32 WA_IT_ERROR-MSG,
 100 SY-VLINE.
 CLEAR : WA_IT_ERROR.
 FORMAT COLOR OFF.
ENDLOOP.
WRITE:/ SY-ULINE(100).
ENDFORM. " DISPLAY_ERROR_REPORT
*& Form CALL_TRANSACTION_FK02
Form used to Call Transaction FK02
form CALL_TRANSACTION_FK02 .
DATA : L_OPTION TYPE CTU_PARAMS,
 L_SUBRC TYPE SYSUBRC.
REFRESH IT_MESSTAB.
CLEAR IT_MESSTAB.
L_OPTION-DEFSIZE = 'X'.
L_OPTION-DISMODE = P_MODE.
L_OPTION-UPDMODE = 'S'.
CALL TRANSACTION 'FK02'
 USING IT_BDCDATA
 MESSAGES INTO IT_MESSTAB
 OPTIONS FROM L_OPTION.
L_SUBRC = SY-SUBRC.
IF L_SUBRC = 0.
 W_SUCC_REC1 = W_SUCC_REC1 + 1.
 WA_IT_succ_rec1-MSG = Text-017.
 IF P_VENMAS = 'X'.
 WA_IT_succ_rec1-LIFNR = WA_IT_VENDOR_MASTER-LIFNR.
 WA_IT_succ_rec1-BUKRS = WA_IT_VENDOR_MASTER-BUKRS.
 ELSEIF P_VENEXT = 'X'.
 WA_IT_succ_rec1-LIFNR = WA_IT_VENDOR_EXTEND-LIFNR.
 WA_IT_succ_rec1-BUKRS = WA_IT_VENDOR_EXTEND-BUKRS.
 ENDIF.
 APPEND WA_IT_succ_rec1 TO IT_succ_rec1.
ELSE.
 IF FL_FLAG3 NE 'X'.
 PERFORM OPEN_BDC_SESSION_fk02.
 FL_FLAG3 = 'X'.
 ENDIF.
 PERFORM BDC_INSERT_fk02.
 W_ERR_REC = W_ERR_REC + 1.
 PERFORM ERROR_RECORD_DATA1.
ENDIF.
endform. " CALL_TRANSACTION_FK02
*& Form OPEN_BDC_SESSION_fk02
Form used to Open session for FK02
form OPEN_BDC_SESSION_fk02 .
DATA : L_USERID TYPE APQ_MAPN, " Variable to hold user-id
 L_GROUP TYPE APQ_GRPN. " Variable to hold value
MOVE P_GROUP1 TO L_GROUP.
MOVE SY-UNAME TO L_USERID.
CALL FUNCTION 'BDC_OPEN_GROUP'
 EXPORTING
 CLIENT = SY-MANDT
 GROUP = L_GROUP
 KEEP = SPACE
 USER = L_USERID
 EXCEPTIONS
 CLIENT_INVALID = 1
 DESTINATION_INVALID = 2
 GROUP_INVALID = 3
 GROUP_IS_LOCKED = 4
 HOLDDATE_INVALID = 5
 INTERNAL_ERROR = 6
 QUEUE_ERROR = 7
 RUNNING = 8
 SYSTEM_LOCK_ERROR = 9
 USER_INVALID = 10
 OTHERS = 11.
IF SY-SUBRC <> 0.
 WRITE:/ TEXT-008. " Unable to open BDC Session
ENDIF.
endform. " OPEN_BDC_SESSION_fk02
*& Form BDC_INSERT_fk02
Form used to insert data into BDC session using FK02
form BDC_INSERT_fk02 .
CALL FUNCTION 'BDC_INSERT'
 EXPORTING
 TCODE = 'FK02'
 TABLES
 DYNPROTAB = IT_BDCDATA
 EXCEPTIONS
 INTERNAL_ERROR = 1
 NOT_OPEN = 2
 QUEUE_ERROR = 3
 TCODE_INVALID = 4
 PRINTING_INVALID = 5
 POSTING_INVALID = 6
 OTHERS = 7.
IF SY-SUBRC <> 0.
 WRITE:/ TEXT-009. " Unable to Insert Data to BDC Session
ENDIF.
endform. " BDC_INSERT_fk02
*& Form display_changed_report
Form to display Updated Vendor data
form display_changed_report .
IF P_VENMAS = 'X'.
 WRITE:/ TEXT-O10. " Updated List for Vendor Master
ELSEIF P_VENEXT = 'X'.
 WRITE:/ TEXT-O11. " Updated List for Vendor Master Extended
ENDIF.
WRITE:/ SY-ULINE(100).
FORMAT COLOR 1.
WRITE:/1 SY-VLINE,
 2 TEXT-H01, " Vendor Number
 17 SY-VLINE,
 18 TEXT-H02, " Company Code
 31 SY-VLINE,
 32 TEXT-H04, " Message
 100 SY-VLINE.
FORMAT COLOR OFF.
WRITE:/ SY-ULINE(100).
LOOP AT IT_succ_rec1 INTO WA_IT_succ_rec1.
 FORMAT COLOR 2.
 WRITE:/1 SY-VLINE,
 2 WA_IT_succ_rec1-LIFNR,
 17 SY-VLINE,
 18 WA_IT_succ_rec1-BUKRS,
 31 SY-VLINE,
 32 WA_IT_succ_rec1-MSG,
 100 SY-VLINE.
 CLEAR : WA_IT_succ_rec1.
 FORMAT COLOR OFF.
ENDLOOP.
WRITE:/ SY-ULINE(100).
endform. " display_changed_report
*& Form display_nochange_report
Form to display No Changed data for Vendors
form display_nochange_report .
IF P_VENMAS = 'X'.
 WRITE:/ TEXT-O12. " No Changes List for Vendor Master
ELSEIF P_VENEXT = 'X'.
 WRITE:/ TEXT-O13. " No Changes List for Vendor Master Extended
ENDIF.
WRITE:/ SY-ULINE(100).
FORMAT COLOR 1.
WRITE:/1 SY-VLINE,
 2 TEXT-H01, " Vendor Number
 17 SY-VLINE,
 18 TEXT-H02, " Company Code
 31 SY-VLINE,
 32 TEXT-H04, " Message
 100 SY-VLINE.
FORMAT COLOR OFF.
WRITE:/ SY-ULINE(100).
LOOP AT IT_noupdate INTO WA_IT_noupdate.
 FORMAT COLOR 2.
 WRITE:/1 SY-VLINE,
 2 WA_IT_noupdate-LIFNR,
 17 SY-VLINE,
 18 WA_IT_noupdate-BUKRS,
 31 SY-VLINE,
 32 WA_IT_noupdate-MSG,
 100 SY-VLINE.
 CLEAR : WA_IT_noupdate.
 FORMAT COLOR OFF.
ENDLOOP.
WRITE:/ SY-ULINE(100).
endform. " display_nochange_report
*& Form ERROR_RECORD_DATA1
Form to get Error Message for Changed Vendors
form ERROR_RECORD_DATA1 .
DATA : L_LINES TYPE I,
 L_MSG(200) TYPE C.
DESCRIBE TABLE IT_MESSTAB LINES L_LINES.
READ TABLE IT_MESSTAB INTO WA_IT_MESSTAB INDEX L_LINES.
IF SY-SUBRC = 0.
 CLEAR L_MSG.
 CALL FUNCTION 'FORMAT_MESSAGE'
 EXPORTING
 ID = WA_IT_MESSTAB-MSGID
 LANG = SY-LANGU
 NO = WA_IT_MESSTAB-MSGNR
 V1 = WA_IT_MESSTAB-MSGV1
 V2 = WA_IT_MESSTAB-MSGV2
 V3 = WA_IT_MESSTAB-MSGV3
 V4 = WA_IT_MESSTAB-MSGV4
 IMPORTING
 MSG = L_MSG
 EXCEPTIONS
 NOT_FOUND = 1
 OTHERS = 2.
 IF SY-SUBRC = 0.
 WA_IT_ERROR_fk02-MSG = L_MSG.
 ENDIF.
 IF P_VENMAS = 'X'.
 WA_IT_ERROR_fk02-LIFNR = WA_IT_VENDOR_MASTER-LIFNR.
 WA_IT_ERROR_fk02-BUKRS = WA_IT_VENDOR_MASTER-BUKRS.
 ELSEIF P_VENEXT = 'X'.
 WA_IT_ERROR_fk02-LIFNR = WA_IT_VENDOR_EXTEND-LIFNR.
 WA_IT_ERROR_fk02-BUKRS = WA_IT_VENDOR_EXTEND-BUKRS.
 ENDIF.
 APPEND WA_IT_ERROR_fk02 TO IT_ERROR_fk02.
 CLEAR WA_IT_ERROR_fk02.
ENDIF.
endform. " ERROR_RECORD_DATA1
*& Form display_error_report_fk01
Form to display Error Report for Master Vendors (FK01)
form display_error_report_fk01 .
IF P_VENMAS = 'X'.
 WRITE:/ TEXT-O05. " Error List for Vendor Master (FK01)
ELSEIF P_VENEXT = 'X'.
 WRITE:/ TEXT-O06. " Error List for Vendor Master Extended (FK01)
ENDIF.
WRITE:/ SY-ULINE(100).
FORMAT COLOR 1.
WRITE:/1 SY-VLINE,
 2 TEXT-H01, " Vendor Number
 17 SY-VLINE,
 18 TEXT-H02, " Company Code
 31 SY-VLINE,
 32 TEXT-H04, " Message
 100 SY-VLINE.
FORMAT COLOR OFF.
WRITE:/ SY-ULINE(100).
LOOP AT IT_ERROR_fk01 INTO WA_IT_ERROR_fk01.
 FORMAT COLOR 2.
 WRITE:/1 SY-VLINE,
 2 WA_IT_ERROR_fk01-LIFNR,
 17 SY-VLINE,
 18 WA_IT_ERROR_fk01-BUKRS,
 31 SY-VLINE,
 32 WA_IT_ERROR_fk01-MSG,
 100 SY-VLINE.
 CLEAR : WA_IT_ERROR_fk01.
 FORMAT COLOR OFF.
ENDLOOP.
WRITE:/ SY-ULINE(100).
endform. " display_error_report_fk01
*& Form display_error_report_fk02
Form to display Error Report for changed Vendors (FK02)
form display_error_report_fk02 .
IF P_VENMAS = 'X'.
 WRITE:/ TEXT-O14. " Error List for Vendor Master (FK02)
ELSEIF P_VENEXT = 'X'.
 WRITE:/ TEXT-O15. " Error List for Vendor Master Extended (FK02)
ENDIF.
WRITE:/ SY-ULINE(100).
FORMAT COLOR 1.
WRITE:/1 SY-VLINE,
 2 TEXT-H01, " Vendor Number

What are function modules used in alv,and its explanation

what are function modules used in alv,and its explanation

hi..
The important function modules are
Reuse_alv_fieldcatalog_merge
Reuse_alv_list_display
Reuse_alv_events_get
Reuse_alv_grid_display
Reuse_alv_commentary_write.
REUSE_ALV_FIELDCATALOG_MERGE
 This function module is used to populate a field catalog which is essential to display the data in ALV.
 If the output data is from a single dictionary table and all the columns are selected, then we need not exclusively create the field catalog. Its enough to mention the table name as a parameter (I_structure_name) in the REUSE_ALV_LIST_DISPLAY. But in other cases we need to create it.
Note : Fieldcatalog can be filled manually also by filling up all the required details into the internal table
The important parameters are:
 1. Export:
 a. I_program_name : report id
 b. I_internal_tabname : the internal output table
 c. I_inclname : include or the report name where all
 the dynamic forms are handled.
 2. Changing
 ct_fieldcat : an internal table with the type
 SLIS_T_FIELDCAT_ALV which is declared in the
 type pool SLIS.
REUSE_ALV_LIST_DISPLAY
This is the function module which prints the data.
The important parameters are:
1. Export:
 I_callback_program : report id
 I_bypassing_buffer : X
 I_buffer_active :
 I_callback_pf_status_set : routine where a user can set
 his own pf status or change the
 functionality of the existing pf status.
 I_callback_user_command : routine where the function codes are
 handled.
 I_structure name : name of the dictionary table
 Is_Layout : structure to set the layout of the report
 It_fieldcat : internal table with the list of all fields and their
 attributes which are to be printed (this table
 can be populated automatically by the function
 REUSE_ALV_FIELDCATALOG_MERGE
 It_events : internal table with a list of all possible events
 of ALV and their corresponding form names.
2. Tables:
 a. t_outtab : internal table with the data to be output
REUSE_ALV_EVENTS_GET: 
 Returns table of possible events for a a list type
1. Import:
 Et_Events :
 The event table is returned with all possible CALLBACK events for the specified list type (column NAME). For events to be processed by the Callback, their FORM field must be filled. If the field is initialized, the event is ignored. The entry can be read from the event table, the field FORM filled and the entry modified using constants from the type pool SLIS.
2. Export:
 I_list_type:
 0 = simple list REUSE_ALV_LIST_DISPLAY
 1 = hierarchical-sequential list
 REUSE_ALV_HIERSEQ_LIST_DISPLAY
 2 = simple block list REUSE_ALV_BLOCK_LIST_APPEND
 3 = hierarchical-sequential block list
 REUSE_ALV_BLOCK_LIST_HS_APPEND
REUSE_ALV_GRID_DISPLAY
A new function from 4.6 version, to display the results in grid rather than a
preview.
Parameters : same as reuse_alv_list_display
REUSE_ALV_COMMENTARY_WRITE
This is used in the Top-of-page event to print the headings and other
comments for the list.
It_list_commentary : Internal table with the headings of the type
 slis_t_listheader.
 This internal table has three fields:
 Typ : H - header, S - selection, A - action
 Key : only when typ is S.
 Info : the text to be printed
plz reward pts if helpful.
regards
vijay.

IS - Retail, What are all the version currently available and what is lates

Hi,
What are all the version currently available and what is latest version?
Regards

Hi akshitha,
1. A logical database is in fact
a program only.
2. This LDB provides two main things :
a) a pre-defined selection screen
which handles all user inputs and validations
b) pre defined set of data
based upon the user selection.
3. So we dont have to worry about from
which tables to fetch data.
4. Moreover, this LDB Program,
handles all user-authorisations
and is efficient in all respects.
5. tcode is SLDB.
1. To get a taste of it.
2. create a new z program.
3. while creating type PNP
in logical database field.
4. paste this code and execute.
REPORT ABC.
infotypes : 0001.
TABLES : PERNR.
GET PERNR.
WRITE :/ PERNR-PERNR.
5. The selection screen which u see
is coming from logical database PNP program.
6. Execute
7. U will get a list of pernr.
SAPDBPNP
this is the main program of LDB PNP
which does the main work.
SAPDB + ldb name.
regards,
amit m.

What are the common errors in reporting and extraction.

hi friends,
what are the common errors in reporting and extraction for implementation and support projects.
thanking u
suneel.

Hi Suneel,
Errors in reporting are like incorrect query creation, errors in creating RKF, CKF and variables, misunderstanding the data, or errors with other tools like broadcasting. Errors in extraction relate to source system connectivity, field-infoobject mapping, incorrect code etc. Also, please search the forums and you will find many real time examples.
Hope this helps...

What are the integration points with sd and qm

hi,
sap gurus,
good morning to all,
what are the integration points with SD and QM.
in r/3.
regards,
balaji.t
09990019711

Dear balaji
Before doing PGI, there will be a preinspection stage where SD will have to integrate with QM. Similarly after sales, whenever there is sales returns, QM will come into picture.
To control the above scenarios, in material master, go to "Quality management" view and click on "Insp.setup" where you need to assign Inspection Types like 04, 06 etc.
thanks
G. Lakshmipathi

AE what are those things that turns on and off in the Project

AE what are those things that turns on and off in the Project

I had was $1,000 credit in September of 2014. In October, I called Digital Juice, because I had a stroke 25 years ago and I told him I would be foolish to give up $1,000 and join Platinum Account. He agreed with me. He then said why don’t you join Platinum Account, and he can update the $1,000 to the account. I said, OK. Then about January 2, $1,000 was in the Platinum Account. I am starting to do some Wedding videos, and I just noticed that the $1,000 credit wasn’t there. What happened to my $1,000? Oh by the way, your Update Status only goes back to December and not back to July.
Rich
"Todd_Kopriva" <[email protected]> said:
AE what are those things that turns on and off in the Project created by ( https://forums.adobe.com/people/Todd_Kopriva ) in After Effects - ( https://forums.adobe.com/message/7122815#7122815 )
I don't understand the question. Please explain in more detail.

What are the differences between ECC5.0 and 6.0 new GL functionality

Hi Experts,
What are the differences between ECC5.0 and 6.0 new GL functionality.
If we want to implement IFRS, I think New GL functionality is very helpful, but why sap is recommending only for ECC6.0 new GL functionality, Eventhough this functionality is available in ECC5.0.
Best Regards,
Dharani

Dear,
ECC 5.0 vs. ECC 6.0/SAP ERP 6.0
Functionality not available in the new G/L with mySAP ERP 2004 and ERP Central Component (ECC) 5.0:
Transfer prices
Statistical key figures
Euro translation
Audit Information System (AIS)
Archiving
Data retention tool
Regards,
Chintan Joshi.

What are criterias to create Config. Scenarios and Comm Channels?

Similar Messages

Maybe you are looking for