Field Exit for Batch Input creation from LSMW

Hi all,
I am having problems getting a field exit to work for validation of user id in the "Create Batch Input Session" step of LSMW.
Program: /SAPDMC/SAP_LSMW_BI_RECORDING
Screen: 1000
Data Element: SYUNAME
Any help would be appreciated.
Regards,
Jason
Message was edited by: Jason Lante

Field exits are not supported after 4.6 yes, but they still work. I found the reason why my field exit wasn't working; it related to the fact that the field I am applying it to is not directly related to a dictionary object. Meaning I cannot apply a field exit.
So my question now is what other ways are there to enhance LSMW?
Regards,
Jason

Similar Messages

What are the User Exits for Sales Order creation process?

Hi,
what are the User Exits for Sales Order creation process? how can I find them?
thanks in advance,
will reward,
Mindaugas

Please check this info:
User Exits In Sales Document Processing
This IMG step describes additional installation-specific processing in sales document processing. In particular, the required INCLUDES and user exits are described.
Involved program components
System modifications for sales document processing affect different areas. Depending on the modification, you make the changes in the program components provided:
MV45ATZZ
For entering metadata for sales document processing. User-specific metadata must start with "ZZ".
MV45AOZZ
For entering additional installation-specific modules for sales document processing which are called up by the screen and run under PBO (Process Before Output) prior to output of the screen. The modules must start with "ZZ".
MV45AIZZ
For entering additional installation-specific modules for sales document processing. These are called up by the screen and run under PAI (Process After Input) after data input (for example, data validation). The modules must start with "ZZ".
MV45AFZZ and MV45EFZ1
For entering installation-specific FORM routines and for using user exits, which may be required and can be used if necessary. These program components are called up by the modules in MV45AOZZ or MV45AIZZ.
User exits in the program MV45AFZZ
The user exits which you can use for modifications in sales document processing are listed below.
USEREXIT_DELETE_DOCUMENT
This user exit can be used for deleting data which was stored in a separate table during sales document creation, for example, if the sales document is deleted.
For example, if an additional table is filled with the name of the person in charge (ERNAM) during order entry, this data can also be deleted after the sales order has been deleted.
The user exit is called up at the end of the FORM routine BELEG_LOESCHEN shortly before the routine BELEG_SICHERN.
USEREXIT_FIELD_MODIFICATION
This user exit can be used to modify the attributes of the screen fields.
To do this, the screen fields are allocated to so-called modification groups 1 - 4 and can be edited together during a modification in ABAP. If a field has no field name, it cannot be allocated to a group.
The usage of the field groups (modification group 1-4) is as follows:
Modification group 1: Automatic modification with transaction MFAW
Modification group 2: It contains 'LOO' for step loop fields
Modification group 3: For modifications which depend on check tables or on other fixed information
Modification group 4: is not used
The FORM routine is called up for every field of a screen. If you require changes to be made, you must make them in this user exit.
This FORM routine is called up by the module FELDAUSWAHL.
See the Screen Painter manual for further information on structuring the interface.
USEREXIT_MOVE_FIELD_TO_VBAK
Use this user exit to assign values to new fields at sales document header level. It is described in the section "Transfer of the customer master fields into the sales document".
The user exit is called up at the end of the FORM routine VBAK_FUELLEN.
USEREXIT_MOVE_FIELD_TO_VBAP
Use this user exit to assign values to new fields at sales document item level. It is described in the section "Copy customer master fields into the sales document".
The user exit is called up at the end of the FORM routine VBAP_FUELLEN.
USEREXIT_MOVE_FIELD_TO_VBEP
Use this user exit to assign values to new fields at the level of the sales document schedule lines.
The user exit is called up at the end of the FORM routine VBEP_FUELLEN.
USEREXIT_MOVE_FIELD_TO_VBKD
Use this user exit to assign values to new fields for business data of the sales document. It is described in the section "Copy customer master fields into sales document".
The user exit is called up at the end of the FORM routine VBKD_FUELLEN.
USEREXIT_NUMBER_RANGE
Use this user exit to define the number ranges for internal document number assignment depending on the required fields. For example, if you want to define the number range depending on the sales organization (VKORG) or on the selling company (VKBUR), use this user exit.
The user exit is called up in the FORM routine BELEG_SICHERN.
USEREXIT_PRICING_PREPARE_TKOMK
Use this user exit if you want to include and assign a value to an additional header field in the communication structure KOMK taken as a basis for pricing.
USEREXIT_PRICING_PREPARE_TKOMP
Use this user exit if you want to include or assign a value to an additional item field in the communication structure KOMP taken as a basis for pricing.
USEREXIT_READ_DOCUMENT
You use this user exit if further additional tables are to be read when importing TA01 or TA02.
The user exit is called up at the end of the FORM routine BELEG_LESEN.
USEREXIT_SAVE_DOCUMENT
Use this user exit to fill user-specific statistics update tables.
The user exit is called up by the FORM routine BELEG-SICHERN before the COMMIT command.
Note
If a standard field is changed, the field r185d-dataloss is set to X. The system queries this indicator at the beginning of the safety routine. This is why this indicator must also be set during the maintenance of user-specific tables that are also to be saved.
USEREXIT_SAVE_DOCUMENT_PREPARE
Use this user exit to make certain changes or checks immediately before saving a document. It is the last possibility for changing or checking a document before posting.
The user exit is carried out at the beginning of the FORM routine BELEG_SICHERN.
User exits in the program MV45AFZA
USEREXIT_MOVE_FIELD_TO_KOMKD
Use this user exit to include or assign values to additional header fields in the communication structure KOMKD taken as a basis for the material determination. This is described in detail in the section "New fields for material determination".
USEREXIT_MOVE_FIELD_TO_KOMPD
Use this user exit to include or assign values to additional item fields in the communication structure KOMPD taken as a basis for the material determination. This is described in detail in the section "New fields for material determination".
USEREXIT_MOVE_FIELD_TO_KOMKG
Use this user exit to include or assign values to additional fields in the communication structure KOMKG taken as a basis for material determination and material listing. This is described in detail in the section "New fields for listing/exclusion".
USEREXIT_MOVE_FIELD_TO_KOMPG
Use this user exit to include or assign values to additional fields in the communication structure KOMPG taken as a basis for material determination and material listung. This is described in detail in the section "New fields for listing/exclusion".
USEREXIT_REFRESH_DOCUMENT
With this user exit, you can reset certain customer-specific fields as soon as processing of a sales document is finished and before the following document is edited.
For example, if the credit limit of the sold-to party is read during document processing, in each case it must be reset again before processing the next document so that the credit limit is not used for the sold-to party of the following document.
The user exit is executed when a document is saved if you leave the processing of a document with F3 or F15.
The user exit is called up at the end of the FORM routine BELEG_INITIALISIEREN.
User-Exits in program MV45AFZB
USEREXIT_CHECK_XVBAP_FOR_DELET
In this user exit, you can enter additional data for deletion of an item. If the criteria are met, the item is not deleted (unlike in the standard system).
USEREXIT_CHECK_XVBEP_FOR_DELET
In this user exit, you can enter additional data for deletion of a schedule line. If the criteria are met, the schedule line is not deleted (unlike in the standard system).
USEREXIT_CHECK_VBAK
This user exit can be used to carry out additional checks (e.g. for completion) in the document header. The system could, for example, check whether certain shipping conditions are allowed for a particular customer group.
USEREXIT_CHECK_VBAP
This user exit can be used to carry out additional checks (e.g. for completion) at item level.
USEREXIT_CHECK_VBKD
The user exit can be used to carry out additional checks (e.g. for completion) on the business data in the order.
USEREXIT_CHECK_VBEP
This user exit can be use to carry out additional checks (e.g. for completion) on the schedule line. During BOM explosion, for example, you may want certain fields to be copied from the main item to the sub-items (as for billing block in the standard system).
USEREXIT_CHECK_VBSN
You can use this user exit to carry out additional checks (e.g. for completion) on the serial number.
USEREXIT_CHECK_XVBSN_FOR_DELET In this user exit, you can enter additional criteria for deletion of the serial number. If the criteria are met, the serial number is not deleted (unlike in the standard system).
USEREXIT_FILL_VBAP_FROM_HVBAP
You can use this user exit to fill additional fields in the sub-item with data from the main item.
USEREXIT_MOVE_FIELD_TO_TVCOM_H
You can use this user exit to influence text determination for header texts. For example, you can include new fields for text determination or fill fields that already exist with a new value.
USEREXIT_MOVE_FIELD_TO_TVCOM_I
You can use this user exit to influence text determination for item texts. For example, you can include new fields for text determination or fill fields that already exist with a new value.
User-Exits for product allocation:
The following user exits all apply to structure COBL, in which the data for account determination is copied to item level.
USEREXIT_MOVE_FIELD_TO_COBL
Option to include new fields in structure COBL.
USEREXIT_COBL_RECEIVE_VBAK
Option to assign values from the document header to the new fields.
USEREXIT_COBL_RECEIVE_VBAP
Option to supply values from the item to the new fields.
USEREXIT_COBL_SEND_ITEM
A changed field can be copied from the structure into the item. You could use the user exit to display a certain field in the account assignment block (see also MV45AFZB).
USEREXIT_COBL_SEND_HEADER
A changed field can be copied from the structure to the header (see source text MV45AFZB)
USEREXIT_SOURCE_DETERMINATION
You can use this user exit to determine which plant will be used for the delivery. In the standard system, the delivering plant is copied from the customer master or the customer-material info record. If you want to use a different rule, then you must enter it in this user exit.
USEREXIT_MOVE_FIELD_TO_ME_REQ
With this user exit you can include additional fields for the following fields:
EBAN (purchase requisition)
EBKN (purchase requisition-account assignment)
USEREXIT_GET_FIELD_FROM_SDCOM
Option to include new fields for the variant configuration. Fields that are included in structure SDCOM can be processed and then returned to the order.
USEREXIT_MOVE_WORKAREA_TO_SDWA
You can use this user exit to format additional work areas for the variant configuration. You will find notes on the user exit in MV45AFZB.
User-Exits for first data transfer:
The following user exits can only be used for the first data transfer.
Note
Only use the user exits if the names/fields do NOT have the same name.
USEREXIT_MOVE_FIELD_TO_VBAKKOM
Option to include additional fields in structure VBAKKOM (communiction fields for maintaining the sales document header)
USEREXIT_MOVE_FIELD_TO_VBAPKOM
Option to include additional fields in structure VBAPKOM (communication fields for maintaining a sales item)
USEREXIT_MOVE_FIELD_TO_VBEPKOM
Option to include additional fields in structure VBEPKOM (communication fields for maintaining a sales document schedule line)
USEREXIT_MOVE_FIELD_TO_VBSN
You can use this user exit to include fields in structure VBSN (scheduling agreement-related change status).
USEREXIT_MOVE_FIELD_TO_KOMKH
You can use this user exit to include new fields for batch determination (document header).
USEREXIT_MOVE_FIELD_TO_KOMPH
You can use this user exit to include new fields for batch determination (document item).
USEREXIT_CUST_MATERIAL_READ
You can use this user exit to set another customer number in the customer material info record (e.g. with a customer hierarchy)
USEREXIT_NEW_PRICING_VBAP
Option for entry of preconditions for carrying out pricing again (e.g. changes made to a certain item field could be used as the precondition for pricing to be carried out again). Further information in MV45AFZB.
USEREXIT_NEW_PRICING_VBKD
Option for entry of preconditions for carrying out pricing again (e.g. changes to the customer group or price group could be set as the preconditions for the system to carry out pricing again). Further information in MV45AFZB.
User-Exits in Program MV45AFZD
USEREXIT_CONFIG_DATE_EXPLOSION
The BOM is exploded in the order with the entry date. You can use this user exit to determine which data should be used to explode the BOM (explosion with required delivery date, for example).
User exits in the program FV45EFZ1
USEREXIT_CHANGE_SALES_ORDER
In the standard SAP R/3 System, the quantity and confirmed date of the sales document schedule line is changed automatically if a purchase requisition is allocated, and it or the sales document is changed (for example, quantity, date).
If you want to change this configuration in the standard system, you can define certain requirements in order to protect your sales orders from being changed automatically. Use this user exit for this purpose. Decide at this point whether the schedule lines are to be changed.
User-Exits in Program RV45PFZA
USEREXIT_SET_STATUS_VBUK
In this user exit you can you can store a specification for the reserve fields in VBUK (header status). Reserve field UVK01 could, for example, be used for an additional order status (as for rejections status, etc.).
The following workareas are available for this user exit:
VBUK (header status)
FXVBUP (item status)
FXVBUV (Incompletion)
USEREXIT_SET_STATUS_VBUP
In this user exit you can you can store a specification for the reserve fields for VBUP (item status).
The following workareas are available for this user exit:
FXVBAP (Item data)
FXVBAPF (Dynamic part of order item flow)
FXVBUV (Incompletion)
USEREXIT_STATUS_VBUK_INVOICE
You can use this user exit to influence billing status at header level.
User exits in the screens
Additional header data is on screen SAPMV45A 0309, additional item data on screen SAPMV45A 0459. These screens contain the Include screens SAPMV45A 8309 or SAPMV45A 8459 as user exits.
Fields which are also to be included in the sales document for a specific installation should be included on the Include screens for maintaining. If an application-specific check module is needed for the fields, this can be included in the Include MV45AIZZ. The module is called up in the processing logic of the Include screens.
For field transports, you do not have to make changes or adjustments.
Example
A new field, VBAK-ZZKUN, should be included in table VBAK.
If the check is defined via the Dictionary (fixed values or check table) the field must be included with the fullscreen editor in the Include screen SAPMV45A 8309. In this case, no change has to be made to the processing logic.
User Exits in Program MV45AFZ4
USEREXIT_MOVE_FIELD_TO_KOMK
You can use this user exit to add or edit additional header fields in the communication structure - KOMK- for free goods determination. For more information, see the New Fields for Free Goods Determination IMG activity.
USEREXIT_MOVE_FIELD_TO_KOMP
You can use this user exit to add or edit additional item fields in the communication structure KOMP for free goods determination. For more information see the New Fields for Free Goods Determination IMG activity.
User Exits in the SAPFV45PF0E and SAPFV45PF0C Programs
EXIT_SAPFV45P_001
You can use this user exit to decide whether intercompany billing data is used in the profitability segment for cross-company code sales, or whether the data comes from external billing (external customer, sales data from the selling company code.
Regards
Eswar

Field Exit For Migo Badi

Hi to all experts,
I need to assign F4 help to a headertext field for MIGO tcode . I have searched all the exits but couldnt find field exit for it. What are the different options fulfilling this requirement.Please help me out

Hi,
    The following are the enhancement/Business Add ins, Please use the appropriate exit for your requirement
Enhancement/ Business Add-in            Description
Enhancement
MB_CF001                                Customer Function Exit in the Case of Updating a Mat. Doc.
MBCF0011                                Read from RESB and RKPF for print list in MB26
MBCF0010                                Customer exit: Create reservation BAPI_RESERVATION_CREATE1
MBCF0009                                Filling the storage location field
MBCF0007                                Customer function exit: Updating a reservation
MBCF0006                                Customer function for WBS element
MBCF0005                                Material document item for goods receipt/issue slip
MBCF0002                                Customer function exit: Segment text in material doc. item
Business Add-in
MB_DOCUMENT_UPDATE                      BADI when updating material document: MSEG and MKPF
MB_DOC_BADI_INTERNAL                    BAdIs During Creation of a Material Document (SAP Internal)
MB_ME_CSGMT_BADI_SAP                    BAdI: Consignment Processing - Stock Transfer
MB_MIGO_BADI                            BAdI in MIGO for External Detail Subscreens
MB_MIGO_ITEM_BADI                       BAdI in MIGO for Changing Item Data
MB_PHYSINV_INTERNAL                     Connection: Core Inventory and Retail AddOn
MB_QUAN_CHECK_BADI                      BAdI: Item Data at Time of Quantity Check
MB_RESERVATION_BADI                     MB21/MB22: Check and Complete Dialog Data
MB_RESERVATION_SCR                      Screen BAdI for Retrofit DFPS
MB_RESERVATION_UPCHD                    BAdI for Creation and Changing of Manual Reservations
MB_RES_BAPI_CHANGE                      BAdI: Execution of Changes to Reservation Fields
MB_RES_BAPI_CREATE1                     BAdI: Adoption of Customer's Own Fields as Reserv. Fields
MB_RES_BAPI_DETAIL1                     BAdI: Display of Customer's Own Fields in Reservations
MB_STOR_LOC_BADI_GTS                    BADI to Check and Change Storage Location (GTS Fct. Only)
MB_DOCUMENT_BADI_SAP                    BADI for Creation and Changing of a Material Document
ARC_MM_EBAN_CHECK                       BAdI: Enhancement of Archivability Check (MM_EBAN)
ARC_MM_EBAN_PRECHECK                    BAdI: Enhancement of Archivability Check (MM_EBAN)
ARC_MM_EBAN_WRITE                       BAdI: Enhancement of Scope of Archiving (MM_EBAN)
ARC_MM_EINA_CHECK                       BAdI: Enhancement of Archivability Check (MM_EINA)
ARC_MM_EINA_WRITE                       BAdI: Enhancement of Scope of Archiving (MM_EINA)
ARC_MM_INVBEL_CHECK                     BAdI: Enhancement of Archivability Check (MM_INVBEL)
ARC_MM_INVBEL_WRITE                     BAdI: Enhancement of Scope of Archiving (MM_INVBEL)
ARC_MM_MATBEL_CHECK                     Prüfung ADD-ON-spezifischer Kriterien für MM_MATBEL
ARC_MM_MATBEL_WRITE                     Check Add-On-Specific Data for MM_MATBEL
MB_CHECK_LINE_BADI                      BAdI: Check Line Before Copying to the Blocking Tables
MB_CIN_LMBMBU04                         posting of gr
MB_CIN_MM07MFB7                         BAdI for India Version exit in include MM07MFB7
MB_CIN_MM07MFB7_QTY                     Proposal of quantity from Excise invoice in GR
MB_DOCUMENT_BADI                        BAdIs During Creation of a Material Document

Using Field Exit for a field in table KNA1

Hi everyone,
I am working on a ticket, the problem is we have a field called STRAS in table KNA1 which holds the address of the customer but now we want to increase the length of this field from 35 charachters to 55 due to some business requirement. SO my question is if this can be done using Field Exit and if yes.. can you please tell me how as I have never used Field exits.
Thanks,
Rajeev

Hi,
Using field exit, you can only validate the data entry for the field (either globally or on a particular screen field)
This is usually done by implementing the field exit for the data element corresponding to the field(in your case STRAS_GP)
Hence you cannot increase the length of the field using the concept of the field exits...
Please note that after SAP R/3 4.6c, SAP has stopped the creation of field exits and there will be no support for any new ones created.
Regards
Shiva

User Exit for batch classification for tcode mb1c

HI experts,
I have implement customer exit MBCFC004 EXIT_SAPMM07M_004 and CLFM0002 EXIT_SAPLCLFM_002 to set a value for
a customize characteristics.
Now I have a issue.
MBCFC004 EXIT_SAPMM07M_004 can work with migo but when I with mb1c to do same transaction it didn't
work.
CLFM0002 EXIT_SAPLCLFM_002 only work when I input a value in the customize characteristics it can change the input value.
I have set extension in OMCV for my move type. and assigned the bath to material.
I have reference
Re: User Exit for batch classification
but I haven't found any question for my solution.
please help me.
thanks a lot.

Class ZBATCH has status 1 (= 'Released') but the customizing of classtype 023 doesn't allow to classify with classes of this status. Settingsfor class status in class type 023 are different from what SAP delivers.Correct please these settings. You may lookup the correct definition of
the class status in class type 022.

Field Exits for XD01.

HI Experts,
I want to implement the Field Exit for Changing the Field discription for Standard sap field for XD01 and MK01.
could any one tell me what are the ( Exits )Field Exits for above T Codes.
Thanks in Advance.
sudeer.

hi,
cherck this link.
http://www.****************/Tutorials/ABAP/XD01/XD01.htm
these r exits available in xd01.
Transaction Code - XD01                     Create Customer (Centrally)
Enhancement/ Business Add-in            Description
Enhancement
SAPMF02D                                User exits: Customer master data
Business Add-in
CUSTOMER_ADDRSCR_CHG                    Change Address Screen in the Master Data Maintenance
CUSTOMER_ADD_DATA                       Additional Data at Customers
CUSTOMER_ADD_DATA_BI                    Additional Data at Customers (Batch Input and ALE)
CUSTOMER_ADD_DATA_CS                    Additional Data at Customers (Subscreen Container 4000)

Customer exit for Batch management

Hi experts,
I'm using customer exit for batch management for internal number assignment.
I need the Batch number as i mentioned below
DDMMYYB01
DD-Date
MM-Month
YY-Year
B-Block
01-Number
For this i need to give logic. How to give i'm not getting. This batch number creation will come at the time of GR.
Anybody help me?
Naren

Hi
Please use the user exit SAPLV01Z as I mentioned in your other thread, please go to SMOD to read its documentstion.
In SMOD, select the 'Documentation' and click 'Display', this will show the overview documentation.
Select the 'Componnet', then ciick the 'Display'. select each component and click 'Documentation Ctrl+F4) this will show the detailed documentation of them.
Best Regards.
Leon.

FIELD exit For WADAT

Hello ,
I have Implemented a field exit for Data element WADAT, but my requrement is, The value In the field LIKP-WADAT in VLO2n/VLO1N TRansaction should not be allowed to change even a single time.
Is there any user exit do statisfy my requirement
cheers.

Field exit can be used to validate a user entry and not restrict a user entry. Even if you implement field exit user can always go and change the contents of field and in field exit ( only triggered in PAI ) there is no way to determine if field value was changed .
You should make the field output only in case you dont want users to change it.
Check if you have BADI LE_SHP_DELIVERY_PROC in your system. In this BADI you can use method CHANGE_FIELD_ATTRIBUTES to set the attributes of LIKP-WADAT in parameter CT_FIELD_ATTRIBUTES to disable input .
Cheers.
Sanjay

Field exit for VA02 / for GOTO- HEADER- SHIPPING

Hello ,
Please help me out with field exit for GOTO->HEADER->SHIPPING in VA02 transaction .
I have to check if the shipping condition enetered against values in TVARV variable .
If unequal i need to display a warining messge .
But the requirement is it needs to be checked against field exit .
Thanks ,
Rahul

Dear Sheo
I know OMJN can set the material Slip mandatory. but my question is how to seperate by company code.
for example:
company code D001 mandatory
company code D002 Input
regards,
Yang

Field Exit for IFCU

Hi experts,
I´m looking for a field exit for transaction IFCU for the first screen.
Does anyone know one?
Best regards,
Fernando Montenegro

Hi Pete,
The first screen for transaction IFCU, shows two fields: The equipment we are trying to record a consumption for and a GasStation field.
The Gas Stations we have configured have this mask: XNN, in which X: is a letter which stands for the company, for example "A" and a number NN for the GasStation belonging to the company in which we will consume fuel, for example 22.
So the GasStation´s name is "A22".
We wish to develop a field in which the user will only have to input the number (for example: "22"), and the system, depending on the company code of the equipment input in the first field, will concatenate the first letter of the company with the number input by the user.
Example:
1.User inputs Equipment that belongs to company "A". <<Enter>>
(System reads Equipment company code, in this case "A")
2.User only inputs "22".
(System concatenates A+22 internally for the GasStation entry)
3.User goes into the next screen to fuel an equipment with the A22 GasStation.
We are trying to find a field/user exit that will do this concatenation internally in the first screen.
I hope I gave you a good idea of what we ´re trying to do.
Thanks a lot and best regards,
Fernando

Incoming IDOC Error "No batch input data from the screen SAPMV45A 4001"

Hello ,
The Incoming IDOC with Message type 'ORDERS' is triggering the error message "No batch input data from the screen SAPMV45A 4001" with message no 00344 . There is an SAP note 785000 to handle this type of error message which has been already implemented. Still we are encountering few IDOC error's at the time of sales order creation. The IDOC reaches status 51 throwing the error which is again reprocessed through BD87 .
We are unable to replicate the similar scenerio in Development & Testing systems as it works fine.
Can any one kindly advise how to eliminate the error "No batch input data from the screen SAPMV45A 4001" message at the time of Incoming IDOC processing.
Thanks in advance.
Best Regards
Sateesh

Dear Sateesh
Check this link where the same topic was discussed
[ VA01/VA02: batch-input error in IDoc processing|http://www.sapfans.com/forums/viewtopic.php?f=21&t=313032]
thanks
G. Lakshmipathi

Script for Batch Exporting XML from IDCS3 files

Does anyone have a script they would share for batch exporting XML from IDCS3 files? I do not know anything about scripting so I do not know how to write one myself. I've also searched around and cannot find anything. I would appreciate any help with this anyone can offer.
Thanks,
Janine

Or use below Code:
try {
     inFolderName= Folder.selectDialog ("Input Folder:");
     outFolderName= Folder.selectDialog ("Output Folder:");
     if ((inFolderName != null) && (outFolderName != null))
          var idFileFolder = new Folder(inFolderName);
          var files = idFileFolder.getFiles("*.indd");
          for(myCounter = 0; myCounter < files.length; myCounter++)
               var theDocument = app.open(File(files[myCounter]));
               with ( theDocument ) {
               myXMLFile = new File(outFolderName + "/" + name.replace(".indd","") + ".xml" );
               exportFile( ExportFormat.xml, myXMLFile );
               close(SaveOptions.no);
catch (err ) {
alert("All files export");
Shonky

Error in generating Batch Input session from FF67 Transn

Hi Folks,
I have tried to create the batch input session from transaction FF67 (Process manual bank statement ) using the menu path settings-->specifications and chosen the option 2 for Processing type, after posting the statement manually, batch is not getting created, is there any settings to be configured apart from this, any help would be highly rewarded.
Thanks in Adv.
Rgds,

Hi Dudes,
Any hint on this issue would be highly helpful ,
Thanks in Advance,
Rgds,

Tracking Deleted Batch Input Map from SM35

Dear All,
I want to find the details of deleted Batch Input Maps from SM35. e.g. if some one deletes a Batch Input Map from SM35 transaction then I need to find the details of the user along with date and time.
I tried finding the table but I could not. Please let me know if this is possible some way.
Regards,
lalit

AFAIK this information is not stored in SAP database
(Check FM BDC_OBJECT_DELETE and include LSBDCF01 form DELETE_SESSION of FG SBDC)
You may ask system to store it in DBTABLOG "Log Records of Table Changes"
- (SE11) Activate the general logging for the table - the technical setting of
the table needs to be adjusted to "Log data changes". To check whether
it is activated for a table, use transaction AUT01.
- (RZ10/RZ11) You may also be required to set the profile parameter rec/client on.
Regards,
Raymond

IDOC/BAPI for Production order creation from Legacy system

Hi all
We are using an interface to create Production orders from legacy to SAP. Would you recommend an IDOC or a BAPI to create Production orders. If IDOC or BAPI then could you please mention which one?
thanks a bunch

Hi John,
For your purposes, please use BAPI for production order creation from legacy system. There is no standard inbound IDoc available to use. SAP has an IDoc for outbound interface only (message type LOIPRO).
If there is an inbound IDoc available, I would recommend to use an IDoc.
IDoc technology has excellent error handling and will allow you to reprocess an error (if any).
BAPI is also good approach to use and fast in term of processing.
For BAPI approach, you can use BAPI BAPI_PRODORD_CREATE.
Hope this will help.
Regards,
Ferry Lianto

Field Exit for Batch Input creation from LSMW

Similar Messages

Maybe you are looking for