Increase of Field length. & vendor data @ sales documents

Dear all,
a. I want to increase the Sales employee - Remarks (field) length from 50 characters to 200 characters.
Can we increase the length of standard field's without using SDK? If yes, tell me how to do?
b. I am creating 2 UDF's @ marketing documents. - Title level
At first UDF - I want to see all the vendor master data (vendor codes) by formatted search
At the secound field - the address of the relevant Ship to r bill to address of vendor has to be filled down - as soon as i selected the vendorcode on the above field.
Can we map the UDF's as per the above requirement - with out using SDK & by using formatted search.
If - we can do with formatted search - help me of how to do & send me the query.
Thanks & Regards
ganesh

Ganesh,
The SAP database field lengths cannot be changed.
Reg the Formatted Search of Vendor Codes for the first UDF. The SQL would be like
SELECT T0.CARDCODE FROM [DBO\].[OCRD\] T0 WHERE T0.CARDTYPE = 'S'
YES, it is possible to trigger the FMS on the second UDF when the Vendor Code is filled in the firt UDF.
I am not clear with what you mean by the following
At the secound field - the address of the relevant Ship to r bill to address of vendor has to be filled down - as soon as i selected the vendorcode on the above field.
The Address information is in CRD1 table and you can use the first UDF's values in the WHERE clause of the SELECT statement in your second FMS
example:
SELECT T0.STREET, T0.CITY, .... FROM [DBO\].[CRD1\] T0 WHERE T0.CARDCODE = $\[ORDR.U_USERFIELD] AND T0.ADRESTYPE = 'B'
CHANGE U_USERFIELD1 with the name of your Vendor Code UDF
T0.ADRESTYPE = 'B' ..........FOR BILLING ADDRESS
T0.ADRESTYPE = 'S' ..........FOR SHIPPING ADDRESS
Suda

Similar Messages

Change IE02 field (Customer/Vendor Data - Operator)

Hello experts,
Does anyone know if there is any BAPI or FM for changing the Operator Field (IE02-> Customer/Vendor Data -> Operator) ???
Any advice/suggestion about how to do this without using a BDC program?
Thanks in advance,
-C

Hi robert,
it will solve your problem.
CUSTOMER_ADD_DATA_CS open for input in display mode
We can use SET_DATA method and parameter i_Activity.
Reddy

Field "OutputType" when assigns sales document header to output procedure

Hi Experts,
When allocates the Output Determination Procedure to Sales doc header (IMG->SD->Basic Functions ->Output Control->Output Determination Using the Condition Technique->Maintain Output Determination for Sales Documents->Assign Output Determination Procedures)
There is a field called "Output type(with all the output type defined)" and i wonder the utility of this field here during assignement of a Output Determination Procedure to Sales document header.
Someone could tell me the use of this field here?
Thank you,
Best regards,
Louis.

Hi,
i m just giving u clue...i think that will answer ur query..
have u created Pricing procedure determination
sales areaDuPPCuPPPricing determination Pricing type
Now can u tell me what is significance of pricing type?
if u know then u answered ur thread query..
correct me if went wrong
tnanks
mk

Can we increase the field length of Packaging material type description

Hi,
The field length allowed for packaging material type description is 20 characters. If i need to have this length to be increased to 25-30.Is it possible?
I mean the description that we give when we create new packaging material type.
Pls let me know ur suggestions.

Hi Dhilipan Nair,
Unfortunately there is no standard way to change this, the desc. field of the view (V_TVTY-VTEXT) is created from the value T685T-VTEXT which has been defined with the Domain TEXT20, so in order to add addition characters to this field, you would need to redefine the preceding field type.
Regards
Stephen

Risks of changing the field length of data structure of a Cluster Table

Hello,
We are on ECC 604 and had implemented HR & Travel Management. Reporting on these applications is done in BI. We use ESS and & Mobile Travel for time, travel expenses, etc and use PCLn clusters.
There is business need to change the length of a field from 20 to 40 for the data structure PTK** of cluster table PCL1.
We are exploring various options to avoid core modifications.
We are also assessing the risks associated with changing the field length.
I am asking you for your opinion about the risks associated with changing the field length of a data structure of cluster table.
Thanks & Regards,
Manoj K Pingali

Recently, we came across the same situation where we had to change the length of a field. Let me explain you what precautions we had taken during that time.
1. Apply the where use list of that table/ Field and check whether it has been used in some program and FM or not. If yes then check one more thing that check the TYPE of another variables on which system has populating data (move, write or in FM parameters). if you will not consider this then you can land you in big trouble. (Conversion dump)
2. Ask the basis to take a dump of the production, quality and data for the safer side if something does not go right.
Now, you can do the changes in your development system and then adjust the database and see the impact of it.
Hopefully, you will not come across any difficult situation in this changes.
Thanks.
Anurag

How to increase the Field length

Hi All ,
I have to increase the Standard Field length in a transaction.
is that possible ? if yes , how we can do that ?
thanks and regards,
Deepak Rana.

it is not advisable to change the format of standard SAP table fields. most of them are being used in many different places, you will have a hard time making sure that all functionality still works OK after such a change.
maybe you can append new fields to ADRC and work with these.
Greetings
Thomas

How can i increase table field length?

Hi all!
Little URGENT!
I am stuck up at one point. I have dmbtr currency field which has 13 length. Now i would like to increse the length of it as per client's requirement.
Can anyone guide me to do that?
Thanks in advance.

Hi Prasad,
DMBTR is standard SAP field having fixed length.If you want to increase the length, you need togo to data element and domain and change there, but it asks accesskey becasue its standard field. Thats is not advisable.
regards
Chandra.
Note: Please reward if helpful.

Problem with increasing input field length in module pool programming.

Hi All,
I have created a screen in which i have used table control wizard. In my table control I have an input field. The problem is, this input filed only takes 23 inputs at a time. I need to make this field unfixed. This is an quantity field. I am not understanding why this is happening. Can anybody plz help me in this regard ?
Thanks in advance.
Tripod.

HI Tripod ,
YOu can add Lines to Table control .
Add one button by name ADD LINES : give func code 'ADD'
IN PBO ...
if it_mat[] is not initial .
    describe table it_mat lines ln .
    tab_ctrl-lines = ln .
endif.
case sy-ucomm .
when 'ADD' .
      perform add_lines .
endcase .
form add_lines .
ln = ln + 1 .
clear it_mat .
append initial line to it_mat .
endform .
regards
deepak.

Reg: Sales document creation

Hi Abapers,
As i am new to SD Module, would like to get some ideas from your end. My requirement is to create a sales order using Programming. After creation of sales order it should post to finance. Could anyone help me how this can be done.

REPORT ZSALESORDER.
* Parameters
* Sales document type
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text FOR FIELD p_auart.
PARAMETERS: p_auart TYPE auart OBLIGATORY.
SELECTION-SCREEN END OF LINE.
* Sales organization
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text1 FOR FIELD p_vkorg.
PARAMETERS: p_vkorg TYPE vkorg OBLIGATORY.
SELECTION-SCREEN END OF LINE.
* Distribution channel
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text2 FOR FIELD p_vtweg.
PARAMETERS: p_vtweg TYPE vtweg OBLIGATORY.
SELECTION-SCREEN END OF LINE.
* Division.
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text3 FOR FIELD p_spart.
PARAMETERS: p_spart TYPE spart OBLIGATORY.
SELECTION-SCREEN END OF LINE.
SKIP 1.
* Sold-to
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text4 FOR FIELD p_sold.
PARAMETERS: p_sold TYPE kunnr OBLIGATORY.
SELECTION-SCREEN END OF LINE.
* Ship-to
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text5 FOR FIELD p_ship.
PARAMETERS: p_ship TYPE kunnr OBLIGATORY.
SELECTION-SCREEN END OF LINE.
SKIP 1.
* Material
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text6 FOR FIELD p_matnr.
PARAMETERS: p_matnr TYPE matnr   OBLIGATORY.
SELECTION-SCREEN END OF LINE.
* Quantity.
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text7 FOR FIELD p_menge.
PARAMETERS: p_menge TYPE kwmeng OBLIGATORY.
SELECTION-SCREEN END OF LINE.
* Plant
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text9 FOR FIELD p_plant.
PARAMETERS: p_plant TYPE werks_d .
SELECTION-SCREEN END OF LINE.
* Complete Deliver
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text10 FOR FIELD p_autlf.
PARAMETERS: p_autlf TYPE autlf DEFAULT 'X'.
SELECTION-SCREEN END OF LINE.
* Data declarations.
DATA: v_vbeln            LIKE vbak-vbeln.
DATA: header             LIKE bapisdhead1.
DATA: headerx            LIKE bapisdhead1x.
DATA: item               LIKE bapisditem OCCURS 0 WITH HEADER LINE.
DATA: itemx              LIKE bapisditemx OCCURS 0 WITH HEADER LINE.
DATA: partner            LIKE bapipartnr OCCURS 0 WITH HEADER LINE.
DATA: return             LIKE bapiret2    OCCURS 0 WITH HEADER LINE.
DATA: lt_schedules_inx   TYPE STANDARD TABLE OF bapischdlx
                         WITH HEADER LINE.
DATA: lt_schedules_in    TYPE STANDARD TABLE OF bapischdl
                         WITH HEADER LINE.
DATA: lt_schedules_ink    TYPE STANDARD TABLE OF bapisdhead1
                         WITH HEADER LINE.
* Initialization.
INITIALIZATION.
v_text   = 'Order type'.
v_text1 = 'Sales Org'.
v_text2 = 'Distribution channel'.
v_text3 = 'Division'.
v_text4 = 'Sold-to'.
v_text5 = 'Ship-to'.
v_text6 = 'Material'.
v_text7 = 'Quantity'.
v_text9 = 'Plant'.
v_text10 = 'Complete delivery'.
* Start-of-selection.
START-OF-SELECTION.
* Header data
* Sales document type
header-doc_type = p_auart.
headerx-doc_type = 'X'.
* Sales organization
header-sales_org = p_vkorg.
headerx-sales_org = 'X'.
* Distribution channel
header-distr_chan = p_vtweg.
headerx-distr_chan = 'X'.
* Division
header-division = p_spart.
headerx-division = 'X'.
headerx-updateflag = 'I'.
*Complete delivery
    header-COMPL_DLV = p_autlf.
    header-COMPL_DLV = 'X'.
* Partner data
* Sold to
partner-partn_role = 'AG'.
partner-partn_numb = p_sold.
APPEND partner.
* Ship to
partner-partn_role = 'WE'.
partner-partn_numb = p_ship.
APPEND partner.
* ITEM DATA
itemx-updateflag = 'I'.
* Line item number.
item-itm_number = '000010'.
itemx-itm_number = 'X'.
* Material
item-material = p_matnr.
itemx-material = 'X'.
* Plant
item-plant    = p_plant.
itemx-plant   = 'X'.
* Quantity
item-target_qty = p_menge.
itemx-target_qty = 'X'.
* item category
itemx-ITEM_CATEG = 'X'.
APPEND item.
APPEND itemx.
*   ITEM DATA
itemx-updateflag = 'I'.
* Line item number.
item-itm_number = '000020'.
itemx-itm_number = 'X'.
* Material
item-material = p_matnr.
itemx-material = 'X'.
* Plant
item-plant    = p_plant.
itemx-plant   = 'X'.
* Quantity
item-target_qty = p_menge.
itemx-target_qty = 'X'.
APPEND item.
APPEND itemx.
*   Fill schedule lines
lt_schedules_in-itm_number = '000010'.
lt_schedules_in-sched_line = '0001'.
lt_schedules_in-req_qty    = p_menge.
APPEND lt_schedules_in.
*   Fill schedule line flags
lt_schedules_inx-itm_number = '000010'.
lt_schedules_inx-sched_line = '0001'.
lt_schedules_inx-updateflag = 'X'.
lt_schedules_inx-req_qty     = 'X'.
APPEND lt_schedules_inx.
*   Fill schedule lines
lt_schedules_in-itm_number = '000020'.
lt_schedules_in-sched_line = '0001'.
lt_schedules_in-req_qty    = p_menge.
APPEND lt_schedules_in.
*   Fill schedule line flags
lt_schedules_inx-itm_number = '000020'.
lt_schedules_inx-sched_line = '0001'.
lt_schedules_inx-updateflag = 'X'.
lt_schedules_inx-req_qty     = 'X'.
APPEND lt_schedules_inx.
* Call the BAPI to create the sales order.
CALL FUNCTION 'BAPI_SALESDOCU_CREATEFROMDATA1'
       EXPORTING
            sales_header_in     = header
            sales_header_inx    = headerx
       IMPORTING
            salesdocument_ex    = v_vbeln
       TABLES
            return              = return
            sales_items_in      = item
            sales_items_inx     = itemx
            sales_schedules_in = lt_schedules_in
            sales_schedules_inx = lt_schedules_inx
            sales_partners      = partner.
* Check the return table.
LOOP AT return WHERE type = 'E' OR type = 'A'.
    EXIT.
ENDLOOP.
IF sy-subrc = 0.
    WRITE: / 'Error in creating document'.
ELSE.
* Commit the work.
    COMMIT WORK AND WAIT.
    WRITE: / 'Document ', v_vbeln, ' created'.
ENDIF.
Code Formatted by: Alvaro Tejada Galindo on Dec 26, 2008 10:58 AM

XL Reporter: Report Designer - Sales Document Type as Column

Hi Everyone,
I have a question regarding report layout in XL Reporter - Report Designer. Here's the scenario:
I have created a Sales Volume Report wherein the report should be able to display the quantity per material per sales document type (Sales Order, Invoice, Credit Memo). The Sales Document type is expanded as Column so that the user can view the total per Sales Document. My problem is, can i re-arrange the order of display of the 3 sales document selected. The current (and I think the default order is alphabethical) which is A/R Credit Memo, A/R Invoice, Sales Order. Can I re - arrange it in my Report Designer so that Sales Order will be the 1st column, followed by the A/R Invoice then lastly the A/R Credit Memo?
Another question, can I change the Display Name of the 3 Sales Document Type? By default, the Sales Document Name is being retrieved by the system. For other fields which where not expanded as column, I can easily change the Display name of the field, but for the sales document, I don't have an idea. Hope anyone can help me.
Thanks in advance.
Malu

If you want the document types in a specific order, don't add as an expansion, but as individual summary comuns, then you can add them in the order you want.
You can use simple Excel formula to rename the columns - hide the row with the column names & add a new row with if statements based on the value in the cell e.g. if (cell = 'Invoice" , "Inv-AR",'')

How to extend the fields length

Hi Experts,
I want to increase the fields length of my BP name in portal .
now it is 40 char in one line but i want 60 char in one line .Can any body send the solution.
Thanx in advance
Regards,
Khurram

Default length of BP Name field is 40 chars in length.You cannot change this ..
Thirumala.

EKES-XBLNR Field Length

In ECC 6.0, the "reference" field on the Confirmation tab of the PO is only 35 characters long. Is there anything out there that will increase the field length to 70?

The domain XBLNR_LONG attach to the field EKES-XBLNR is of
35 Character String.
In standard system it is not possible to customize the field
EKES-XBLNR length to more than 35 character. Because field length is defined   at domian level which effects at system level i.e all applications   ,trasations etc.If you want to change the field
EKES-XBLNR lenegth to more than 35 char then you need to change this at database level i.e    domain level in tcode SE11
Please note that if you change at domain level then will effect to all other applications also.

Regarding number ranges for sales documents.

Dear Guru's,
There are 2 number range fields in defining a sales document(i.e Int. & Ext.).
Actually we specify either internal or external ,but if we specify both what will happen.
Thanks in advance,
Cherukuri

Hi,
The number ranges can be either external or internal. If it is external internal you need to mark it in the VN01 and at the same time delete the internal assignment number in the VOV8. If the internal assignment field in VOV8 is not blank the system will keep generating internal numbers.
If it is external no. range the current no. that is being used cannot be seen on the VN01 screen. And while creating the sales order itself the sytem will prompt you to enter a number between the available range. If you dont enter the same system will not allow you to proceed further.
Kind Regards
Chakradhar

Indicator in Sales Document type

Hi Gurus,
what is the use of the field Indicator in the Sales Document Type while defining VOV8.
What exactly the use of it.
Thanks & Regards
VASU

mr.vasu
indicator in sales documents clasifies the document type.it is only for to display in TVAK table.TVAK table is the table where all the sales document types going to be stored.
vijaya rajendra.g
reward if it is useful.

CO-PA Value Field from Sales Document: Item Data

Hi,
I need to see a field from sales document.
This field is "volume" and it is in table VBAP, field VOLUM.
Can any body give a hint how should I configure the system to get data on a value field if I want to run a report?
Thanks
G

Try creating a characteristic from VBAP. KEA5 is the tcode. Create a new characteristics from table VBAP and pick VOLUM. Then it will be availble for u in COPA.

Increase of Field length. & vendor data @ sales documents

Similar Messages

Maybe you are looking for