Hi Karthik,
1. Under the 'Data' tab for the table icon, pass the internal table which contains the data and the work area
2. The width of the table cell in the Smartforms editor needs to be increased to accommodate the UOM value. 
Sometimes the UOM characters being of 3 characters we tend to make the width too narrow, and it does not show up in the print (even though you find data in the workarea in debug mode).
Try and let me know.
Thanks Maria. I believe your recommendation would have worked however it would have had the users enter notification data before the check would be made. I appreciate the time you took to offer this suggestion!
Thanks Makesh. Implemented an implicit enhancement in the PAI field module and works perfect!
Hi,
Thanks for your reply, could I use this badi to check my "Z" fields of the ME51N?
Best regards
Hi
You need to create a internal table same as you have in table control.and work area.
loop at internal table where you have data into new work area.
\
WHEN'MOVE'.
"Retrieving record selected
LOOPAT it1 INTO wa1 WHERE MARK = 'X'.
"Making records being not selected
CLEAR wa1-MARK.
"Moving record to destination table
APPEND wa1 TO it2.
ENDLOOP.
Hi Ankit,
What should be written inside Module .......................? Modify statement because 1st one passing data directly to W_EKPO from EKPO, now I want to change from Table Control Input..
Sorry I want to check the ME51N too can I use the same badi?
Yes,, helpful answer, but suppose i am using any variable any variables where I have to declare in smartform .... and how?
Hello Frederic,
Thanks for the quick response.
I know about creating the WebDynpro and link it to a workflow, but is it possible to modify the SAPGUI logon page and insert "Forgot My Password" just below the Language? Have never seen it done before.
Thanks
DS
I developed a program which uses GOS attachments list to allow attachment of files. In a subsequent step, those attachments must be read and processed. So, I read the file contents using (according to note 927407) class CL_BINARY_RELATION and afterwards function module SO_DOCUMENT_READ_API1.
The problem is that when processing those contents, files end up damaged. It happens particularily with DOCX / PPTX / XLSX files (newer office formats).
If I download (using GUI_DOWNLOAD) or email (using CL_DOCUMENT_BCS->ADD_ATTACHMENT) those files, upon opening the corresponding office applications warn that the file is damaged, and repair it.
Comparing CONTENT_HEX with the DATA_TAB from GUI_UPLOAD of the same file (DIFF tool in debugger), I've narrowed the difference to the last bytes of the table. On GUI_UPLOAD one (undamaged file), the end is "0000000000...", while the one returned by SO_DOCUMENT_READ_API1 is "0202020202..."
I've seen that inside SO_DOCUMENT_READ_API1, the hex content is filled up using the text content, by function module SO_SOLITAB_TO_SOLIXTAB.
I've tried to work around this by converting myself instead using CL_BCS_CONVERT=>SOLI_TO_SOLIX, but the same happens.
I've run out of ideas and found no SMP note on this so if anyone else had the same problem, please help.
Thanks
Hi
You need to confirm the Page Size specified in the smartform is matches with the Printer configuration using SPAD.
Regards,
Venkat
Hello Vishal ,
There is no BAPI as such available ,
But there are Automatic Progragram available for clrearing .
Or you will have to Run a BDC recording if you want to have any specific variation during clearing .
Hello Sachin,
Have you tried using DISPLAY LIKE addtion in your message statement .
.
Hope this helps ,
Anup
Hello Ankan ,
I din't got your problem though ,
But Why do you want to read the excel in your internal table you will have to develop logic to fill in the BDC field accoridn to your required by reading it from the internal table.
As suggested by Sai a bapi will be much better option .
Hope it helps,
Anup
There can be Whole Custom thing ,
But how are you going to explain this to your vendor ....! As purchase over is one Whole document for Vendor.
After maybe 10 years of ALV SAP discovered that actually ALV can build the field catalog itself. This is done using the object model CL_SALV classes.
If you still want to use the 'old' ALV technologies or must use the editable ALV, you can still use the object model to get the field catalog for any internal table:
I published a method for this:
You may easily make a FORM routine or a function module if you do not like methods. Then use it whenever you use ALV.
Regards
Clemens
Hi,
You will have to achieve this with TRANSFORMATIONS. Check the Link below:
wiki.sdn.sap.com/wiki/display/Snippets/XML+XLS+transformation
Should be helpful.
Cheers,
Arindam
Hi,
Just put in your conditions in the conditions tab of your windows.
Cheers,
Arindam
Hi,
The list of exits and BADI available is quite a lot you can check from the available list below:
Enhancement
MEQUERY1 Enhancement to Document Overview ME21N/ME51N
MEVME001 WE default quantity calc. and over/ underdelivery tolerance
MM06E001 User exits for EDI inbound and outbound purchasing documents
MM06E003 Number range and document number
MM06E004 Control import data screens in purchase order
MM06E005 Customer fields in purchasing document
MM06E007 Change document for requisitions upon conversion into PO
MM06E008 Monitoring of contr. target value in case of release orders
MM06E009 Relevant texts for "Texts exist" indicator
MM06E010 Field selection for vendor address
MMAL0001 ALE source list distribution: Outbound processing
MMAL0002 ALE source list distribution: Inbound processing
MMAL0003 ALE purcasing info record distribution: Outbound processing
MMAL0004 ALE purchasing info record distribution: Inbound processing
MMDA0001 Default delivery addresses
MMFAB001 User exit for generation of release order
MRFLB001 Control Items for Contract Release Order
MELAB001 Gen. forecast delivery schedules: Transfer schedule implem.
AMPL0001 User subscreen for additional data on AMPL
LMEDR001 Enhancements to print program
LMELA002 Adopt batch no. from shipping notification when posting a GR
LMELA010 Inbound shipping notification: Transfer item data from IDOC
LMEQR001 User exit for source determination
LMEXF001 Conditions in Purchasing Documents Without Invoice Receipt
LWSUS001 Customer-Specific Source Determination in Retail
M06B0001 Role determination for purchase requisition release
M06B0002 Changes to comm. structure for purchase requisition release
MEFLD004 Determine earliest delivery date f. check w. GR (only PO)
MEETA001 Define schedule line type (backlog, immed. req., preview)
ME590001 Grouping of requsitions for PO split in ME59
M06E0005 Role determination for release of purchasing documents
M06E0004 Changes to communication structure for release purch. doc.
M06B0005 Changes to comm. structure for overall release of requisn.
M06B0004 Number range and document number
M06B0003 Number range and document number
Business Add-in
ME_PROCESS_PO Enhancements for Processing Enjoy Purchase Order: Intern.
ME_PROCESS_COMP Processing of Component Default Data at Time of GR: Customer
ME_PO_SC_SRV BAdI: Service Tab Page for Subcontracting
ME_PO_PRICING_CUST Enhancements to Price Determination: Customer
ME_PO_PRICING Enhancements to Price Determination: Internal
ME_INFOREC_SEND Capture/Send Purchase Info Record Changes - Internal Use
ME_HOLD_PO Hold Enjoy Purchase Orders: Activation/Deactivation
ME_GUI_PO_CUST Customer's Own Screens in Enjoy Purchase Order
ME_FIELDSTATUS_STOCK FM Account Assignment Behavior for Stock PR/PO
ME_DP_CLEARING Clearing (Offsetting) of Down Payments and Payment Requests
ME_DEFINE_CALCTYPE Control of Pricing Type: Additional Fields
ME_COMMTMNT_REQ_RE_C Check of Commitment Relevance of Purchase Requisitions
ME_COMMTMNT_REQ_RELE Check of Commitment Relevance of Purchase Requisitions
ME_PROCESS_PO_CUST Enhancements for Processing Enjoy Purchase Order: Customer
SMOD_MRFLB001 Control Items for Contract Release Order
MM_EDI_DESADV_IN Supplementation of Delivery Interface from Purchase Order
MM_DELIVERY_ADDR_SAP Determination of Delivery Address
ME_WRF_STD_DNG PO Controlling Reminder: Extension to Standard Reminder
ME_TRIGGER_ATP Triggers New ATP for Changes in EKKO, EKPO, EKPV
ME_TRF_RULE_CUST_OFF BADI for Deactivation of Field T161V-REVFE
ME_TAX_FROM_ADDRESS Tax jurisdiction code taken from address
ME_REQ_POSTED Purchase Requisition Posted
ME_REQ_OI_EXT Commitment Update in the Case of External Requisitions
ME_RELEASE_CREATE BAdI: Release Creation for Sched.Agrmts with Release Docu.
ME_PURCHDOC_POSTED Purchasing Document Posted
ME_PROCESS_REQ_CUST Enhancements for Processing Enjoy PReqs: Customer
ME_PROCESS_REQ Enhancements for Processing Enjoy PReqs: Internal
ME_COMMTMNT_PO_REL_C Check for Commitment-Relevance of Purchase Orders
ME_CCP_BESWK_AUTH_CH BAdI for authorization checks for procuring plant
ME_CCP_ACTIVE_CHECK BAdI to check whether CCP process is active
ME_BSART_DET Change document type for automatically generated POs
ME_BAPI_PR_CREATE_02
ME_BAPI_PR_CREATE_01
ME_BAPI_PO_CREATE_02
ME_BAPI_PO_CREATE_01
ME_BADI_DISPLAY_DOC BAdI for Internal Control of Transaction to be Invoked
ME_ACTV_CANCEL_PO BAdI for Activating the Cancel Function at Header Level
MEGUI_LAYOUT BAdI for Enjoy Purchasing GUI
EXTENSION_US_TAXES Extended Tax Calculation with Additional Data
ARC_MM_EKKO_WRITE BAdI: Enhancement of Scope of Archiving (MM_EKKO)
ARC_MM_EKKO_CHECK BAdI: Enhancement of Archivability Check (MM_EKKO)
ME_CCP_DEL_DURATION Calc. of Delivery Duration in CCP Process (Not in Standard)
ME_COMMTMNT_PO_RELEV Check for Commitment-Relevance of Purchase Orders
ME_COMMITMENT_STO_CH BadI for checking if commitments for STOs are active
ME_COMMITMENT_RETURN Commitment for return item
ME_CIP_REF_CHAR Enables Reference Characteristics in Purchasing
ME_CIP_ALLOW_CHANGE Configuration in Purchasing: Changeability Control
ME_CIN_MM06EFKO Copy PO data for use by Country version India
ME_CIN_LEINRF2V BADI for LEINRF03 excise_invoice_details
ME_CIN_LEINRF2R BADI for CIN India - Delivery charges
ME_CHECK_SOURCES Additional Checks in Source Determination/Checking
ME_CHECK_OA Check BAdI for Contracts
ME_CHECK_ALL_ITEMS Run Through Items Again in the Event of Changes in EKKO
ME_CHANGE_OUTTAB Enrich ALV Output Table in Purchasing
ME_CHANGE_CHARACTER Customer-Specific Characteristics for Product Allocation
Cheers,
Arindam
Hi Nagaraju/Guru,
I have modified Guru's Code a bit and the below code works perfectly fine for your need Nagaraju.
The red part is the main logic for clearing the selection screen data after execution.
*&---------------------------------------------------------------------*
*& Report Z_DYNAMIC_LIST
*&
*&---------------------------------------------------------------------*
*&
*&
*&---------------------------------------------------------------------*
REPORT z_dynamic_list.
TYPE-POOLS: vrm.
PARAMETERS: p_test AS LISTBOX VISIBLE LENGTH 10.
DATA: it_list TYPE vrm_values,
wa_list LIKE LINE OF it_list.
AT SELECTION-SCREEN OUTPUT.
CLEAR: wa_list,
it_list[].
wa_list-key = '1'.
wa_list-text ='Testing1'.
APPEND wa_list TO it_list.
CLEAR wa_list.
wa_list-key = '2'.
wa_list-text ='Testing2'.
APPEND wa_list TO it_list.
CALL FUNCTION 'VRM_SET_VALUES'
EXPORTING
id = 'P_TEST'
values = it_list.
END-OF-SELECTION.
WRITE : 'Junk'.
FIELD-SYMBOLS : <fs> .
ASSIGN ('(RSDBRUNT)MEMKEY-INT_MODE') TO <fs> .
IF sy-subrc = 0 .
<fs> = '01' .
ENDIF.
Please revert in case anything is not clear.
regards,
Ankit.