Transporter Field in GR

Dear Experts
I want to input Transporter name in GR Screen at the time of MIGO. Is there any field in GR Screen to capture the Transporter name?
Thanks

Hi,
Take the help of your ABAPer who would try this on Sandbox / Dev Server to see if it meets your requirement of capturing the
field of Transportation.
If it does not solve your purpose, then you would have to go in for a Screen Development which will require Using another User Exit to capture the Data in a new Table with a Validation check. This is a major enchancement and needs to be done very carefully as it might create inconsistencies in the system if not done properly.
Try to use this User Exit it might serve your purpose : MCP20023
User Exit for Checking Duplicate Char. Combination.
It is Strongly recommended that this is to be done in SANDBOX / DEV server to see the results.
Hope it helps,
Best regards
Amit Bakshi

Similar Messages

How to make means of transport field as a mandatory field in MV45AFZZ

Hi All,
I am new to User-Exits.
In Sales Order creation I have got a requirement In such a way that based on Sold to and Shipto Party Combination of sales order
I have to make Means of Transport Field as a Mandatory Field.
I have gone through the Program MV45AFZZ.
Please let me know how to do it .
Regards.
Rohit.

Hi ,
Write code in Save_Document_prepare In program MV45AFZZ.
Constant :c_flag type c .
if c_flag eq space.
IF VBAK-VSBED EQ '01' AND VBKD-TRATY IS INITIAL.
MESSAGE E0001(SABAPDOCU) WITH 'Enter means of transport'.
endif.
c_flag = 'X'.
endif.
Regards.
Eshwar.

MIR7 - Transport RSEG fields (Append Structure) to BSEG

Dear enhancers
I would like to ask you haw could I approach such a requirement:
The RSEG table is appended 2 more ZZ_ fields. Let's say it's ZZ_A and ZZ_B fields.
Those fields are populated by the MIR7 transaction. I've got a Z-tab added in line items section. It is used via MRM_INVOICE_POST BAdI implementation. User may specify ZZ_A and ZZ_B fields for each line item of logistisc invoice.
Now my task is:
When posting document from MIR7 transaction transport fields ZZ_A and ZZ_B in such way:
RSEG-ZZ_A -> BSEG-XREF1
RSEG-ZZ_B -> BSEG-XREF2
And my question is how should I approch this task?
I can see there are several ENHANCEMENT-POINTS in MRM_INVOICE_POST FModule. But my experirnce with enhancements is a bit poor. How can I know which enhencement point could I potentially use? Am I able to find out somehow that for example
"Enhancement point A is used for transport fields blablabla ..." some kind of enhancement description.
I will be very thankful for your suggestions. Regards. P.

Hi,
1.- chek this thread:
here The specified item was not found. says the following:
Now go to MRM_INVOICE_POST function module, just before the call of function module CKMV_AC_DOCUMENT_CREATE, I have created an enhancement spot and changed the XACCIT-XREF1 with RBKPV-custom field value.
2.- Another possibility
although it is not an enhancement-point (it´s BADI AC_DOCUMENT) maybe this could be useful to you:
http://blog.csdn.net/xyfchris/archive/2007/10/04/1811359.aspx
Best regards.
Edited by: Pablo Casamayor on Dec 9, 2009 1:32 PM

Concatenate a field in internal table without loopat.

In an internal table,
I need to update one field (all rows) concatenate that field with a value say '999'.
Is it possible to do this in a single MODIFY statement without using loopat condition or any other best possible way to do it?

yes, it is possible without LOOP:
MODIFY itab FROM workarea WHERE condition TRANSPORTING field.
workarea has to like a single line of the internal table and has to contain the value you want to transfer
after TRANSPORTING you name the field you want to change
you can check the complete syntax (with examples) in SAPHelp

PM Reports: Need to find the sum of a particular field in the output.

Hello Experts,
                      I have an issue. I have developed the report to calculate the power per ton. It is PM module.
Input is : DATE & Measuring Point.
Output required is : For a particular date , What is the power consumed per ton.
Its is calculated by the formula Power consumed per day / Production.
I have multiple entries for production ( because different material are used ) per date and a single entery for power (because power is taken as total power consumed per day)
Hence im getting the output as
For example:
date                power            production         power/ton
01.03.2011      5000                    100                  50.00
01.03.2011      5000                      50                 100.00
01.03.2011      5000                      25                 200.00
01.03.2011      5000                      75                  66.66
The desired result is
date                power            production         power/ton
01.03.2011      5000                    250                  20.00
I need to sum the production field.
How can I achieve this ?
Please help.

Hello
Rotate the loop and use event so on change just clear the variable based date condition .
take 2 temp variable for summation
clearing the total and moving value on permanent variable means modifying the itab.
loop at .
*Clear
on change <datefield>.
modify itab from wa transporting <field name> .
clear <total field>.
endon.
*Total
t_prd = t_prd + production..
t_power = t_power + power .
endloop.

Need a document for field exit....urgent

Can any one please send a document for field exit or have a simple document on how to work on a field exit with screen shots. pls send it ...its urgent
Thanks and regards
Nandha kumar R

Hi,
A field exit is a type of user exit.
A user exit is a hook where you can inject your own add-on functionality or behavior to SAPs standard business applications without having to modify the original applications.
Field exits allow you to create your own programming logic for any data element in the Dictionary. You can use this logic to carry out checks, conversions, or business-related processing for any screen field.
Field Exits
Field exits allow you to create your own programming logic for any data element in the Dictionary. You can use this logic to carry out checks, conversions, or business-related processing for any screen field. Example: The data element BBBNR identifies a companys international location number. You might want to set up your R/3 System so that all international location numbers are larger than 100.
The field exit concept lets you create a special function module that contains this logic.
You assign the special function module to the data element BBBNR. You then assign the module to any programs and screens in which users can add new international location numbers. When you activate your field exit, the system automatically triggers your special routine whenever a user enters a company location number.
In 4.6c, you can use "RSMODPRF" program to create field exits.
An example of a user exits :-
MODULE user_exit_0001 INPUT
    CASE okcode.
        WHEN 'BACK OR EXIT'.
            CASE sy-dynnr.
                    WHEN '100'.
                         SET SCREEN 0.
                         LEAVE SCREEN.
                    WHEN '200'.
Note that you can write any code that satisfy your needs.                                                     ****
But in this case, this was wrote as a sample code for reference sake.                                    ****
And you can test it.                                                                                ****
                         SET SCREEN 100.
                         LEAVE SCREEN.
             ENDCASE.
      ENDCASE.
Field exits (SMOD/CMOD) Questions and Answers
1. Field exit was created with CMOD, but is not processed when calling the screen.
- Since the field exit is not processed until PAI, an action must be triggered on the screen (Return, Save, ...).
- Set profile parameter abap/fieldexit to YES and restart the system.
- After activating the function module FIELD_EXIT... and the field exit, leave the transaction on whose screen the field exit is to be executed. The screen is not generated until the transaction is started.
- Do not work on different application servers since there may be some delay before the field exit is activated.
- The profile parameter must be set on all or none of the application servers.
- If the field exit is to only be active on specific screens, check whether you chose the correct program and the correct screen
      number (take care with subscreens).
- Using SE51 -> Field list, check that the screen field does have a reference to a data element. In the name of the field exit use the name of the data element and not the field name.
- After transport, field exits are marked as active but will not be processed.
   Tip: First try deactivating the field exit once more and then afterwards, activate it again.
2. How is performance affected by setting abap/fieldexit?
- If a screen is generated and the profile parameter is set, a check is run on 2 tables (TDDIR, TDDIRS) to see whether a field exit must be generated for the respective field. In practice, the screen load is not generated until the screen is selected after an
update. The user should not notice any difference because screen generation is very fast.
3. Can you read the contents of other screen fields in the field exit?
- In principle, every field exit can store its value in the global variables of the function group (TOP) and hence make them
available to other field exits. Note here that field exits are always called and not only if an entry is made in the field or if the field is empty. In addition, it is not possible to make any assumptions about the order in which the field exits will be called in the future.
4. How does the field exit behave on step loop fields ?
- After the user has entered data, the field exit is called in PAI as often as there are visible fields in the step loop. The system
variable SY-STEPL is incremented each time. If a new value is assigned to the field, it is displayed in the module between LOOP and ENDLOOP. This module is also called once for each visible step loop line.
5. Can field exits be debugged ?
- No. Field exits must be tested separately in the ABAP/4 Development Workbench. For errors which only occur in the screen environment, it is helpful to write interesting variable to the file system using TRANSFER... . These can then be analysed there.
6. What can you do if the field contents are no longer transported to to ABAP/4.
- Check whether a value is assigned to the field OUTPUT.
7. When is the field exit called if a conversion exit is attached to the
   data element ?
- The field exit is called after the conversion exit. This means that the INPUT field receives the data in the same format as the
ABAP/4 program also receives it.
8. Although a global field exit is inactive, a function module is called which does not exist (for example FIELD_EXIT_PROGRAMM_@)
- This is an error in the kernel which no longer occurs as of 3.0C. As a temporary measure, it is useful to assign a program and a screen which do not exist to the field exit and then activate the field exit.
9. Field exit is not visible in CMOD, although created.
- If you want to create a field exit for a data element, a function module is proposed with the name FIELD_EXIT_. This
function module must exist for the field exit to work. If you do not create this function module, but do create one with a suffix,
the data element is not displayed in CMOD.
10. Field exit is not executed although it is active.
- Fields which do not have the 'Input field' attribute usually do not trigger a field exit. The field exit is designed to allow an
extended input check. It is therefore only called for input fields - even if they are not ready for input at runtime of the         application by LOOP AT SCREEN.
This rule does not apply, however, if the field is located within a steploop. Here the field will be always activated, even if it is
invisible.
- Field exits can only be executed for fields that are directly related tothe dictionary. If the relation is indirect, i.e. via an       ABAP declaration ( LIKE ), no field exit can be executed.
11. Field exits on check buttons do not work
- Field exits are only intended for input fields. As check buttons count as graphical elements, you cannot install field exits on
them.
12. Field exits do not work on selection screens
SAP Field Exits
From 4.6c onwards, Field exits will no more be supported by SAP. They removed the function of field exit but they had given lot of flexibility through userexit.
However, if you still required it, here is how to activate it :-
First called up transaction CMOD.
Then called up transaction PRFB.
or
Activation of the field exits and assignment of the dynpros can also be carried out using program RSMODPRF. For this purpose, the program must be started without parameters (input fields remain blank). If required, new field exits can be created using program RSMODPRF (see the program documentation).
REFER THIS LINK ALSO.
defining screen fields using FIELD-SYMBOL
Thanks,
Shankar

Report Template with WWI: Waste Transporter: License Plate

Hi all,
I am trying to create a WWI document for Disposal Document.
I want to introduce the License Plate. I suppose that i have to introduce it in some waste transporter field , but i dont find it.
Can anyone help me? thank you very much. Marí

Thanks keshav,
I will try to explain it to you:
I need to print in my out put doc the licence plate.
Actually i can do it and it appears correctly in my output doc, but before, in the disposal document (WAM02), i have to introduce it manually (in the license plate field, that is in the waste transporter worksheet).
I think that this field (WAM02) is inherance from the waste transporter (WAA19) like other fields like: name, Number Assigned by Authority for Partner, etc...
so, i have to introduce the licence plate in some field of the transporter, but i do not know where is it.
Best regards. María.

Field exit for cmod

Hi,
Field exit was created with CMOD, but is not processed when calling the screen.
Thanks,
Biju

Hi Biju,
Please find below an extract on how to approach the problem
1. The field exit was created with CMOD, but is not processed when the screen is called.
Field exits can be defined only for data elements whose name is shorter than 19 characters. The name of the data element plus the prefix "FIELD_EXIT_" must not exceed the maximum length of a function module name (30).
Since the field exit is not processed until PAI, an action must be triggered on the screen (choose enter, save, and so on).
Set the profile parameter abap/fieldexit = YES and restart the system.
After activating the function module FIELD_EXIT... and the field exit, leave the transaction on whose screen you want to execute the field exit. The relevant screen is only generated when the transaction is called.
Do not work on different application servers since there may be some delay before the field exit is activated.
The profile parameter must be set on all or no application servers.
If the field exit is to only be active on specific screens, check whether you chose the correct program and the correct screen number (take care with subscreens).
Use transaction SE51 to generate the screen on which the exit should be active. It is possible that it was not correctly generated. If you want to be sure that all screens that use the data element are regenerated, you can copy the report rsmodfdg from the correction instructions and start it with transaction SE38. The report uses the affected data element as the input parameter and regenerates all screens that use the data element.
Use transaction SE51 and choose 'Field list' to check that the screen field actually has a reference to a data element. In the name of the field exit, use the name of the data element and not the field name.
After the transport, field exits are marked as active but are not processed. Tip: First try to deactivate the field exit once more and then activate it again.
http://www.saptechies.com/faqs-field-exits-cmod/
Regards
Byju

Transports not visible after CTS+ Deploy

Hi,
We have configured CTS+ in our XI landscape. The XI objects are succesfully getting transported to QA from Dev and when transporting from QA to PRD the deployment is happening without errors but we are not able see those transports in the PRD.
Transport log is has no errors and it is calling the right system.
Here with attaching the transport log
Log File:
devsappi.abbgrain.local\sapmnt\trans\log\DPXT900068.PTX
     3T             ######################################
        Deployment
        Transport request   : DPXK900068
             System              : PTX
        tp path             : tp
        Version and release: 372.04.10 700
     3T             CTS Deploy Service - Version 0.92 06.03.2007
        ========================================================================
        Deploy web service destination = CTSDEPLOY
        Directory =
devsappi.abbgrain.local\sapmnt\trans\data
        SDM Deploy URL =
        SLD Deploy URL =
        XI Deploy URL = http://prodsappi.abbgrain.local:53000
        Double-stack system PTX
        Deploy for XID
        Deploy File = 5df706c0307511dd9b0e005056b9061c
        Start of Web Service Log
        Deploy Service called with following parameters:
        CommunicationData-Type:1
        CommunicationData-Address:http://prodsappi.abbgrain.local:53000/dir
        CommunicationData-Host:prodsappi.abbgrain.local
        CommunicationData-Port:53000
        CommunicationData-User:'filled'
        CommunicationData-Password:'filled'
        Deployable(0)
        Deployable-Type:1
        Deployable-Id:
devsappi.abbgrain.local\sapmnt\trans\data/DPXK900068/5df706c0307511dd9b0e005056b9061
        >>>c
        Importing archive:
devsappi.abbgrain.local\sapmnt\trans\data/DPXK900068/5df706c0307511dd9b0e005056b
        >>>9061c
        Import finished sucessfully
        End of Web Service Log
        Return Code = 0
        Highest Return Code = 0
        Deployment
        End date and time : 20080714174834
             Ended with return code: ===> 0 <===
Please suggest what could be the problem and where I can cross verify.
Thanks & regards
Mrutyunjay

Hi Mrutyunjay,
directory transports are not activated automatically. With the CTS+ import to the directory a changelist containg the objects is created under the service user used for the target system in the XI TMS configuration.
You have to takeover the changelist from the service user, adjust the "non-transportable" fields of the objects in the changelist, and finally activate the changelist,
Afterwards the objects should exist in the target directory.
Best regards,
Silvia

Is it possible to work with Field Exits in R/3 Enterp. Basis 6.20???

How could I work with them?

Yes you can.
SE 38 --> Prog RSMODPRF
http://www.sapdevelopment.co.uk/enhance/fexits.htm
But Have a look at OSS note 29377 as well:
Symptom
Problems and questions concerning field exits
Other terms
FAQ, Q+A, SMOD/CMOD, field exits
Reason and Prerequisites
Note
Field exits are frozen on the 4.6C maintenance level and are not further developed. This means that the existing functionality is kept with all restrictions (see also the last item below). Existing exits can be further used and are called at runtime as usual.
Existing exits can be maintained using program RSMODPRF (run the
program using transaction SE38). Activation of the field exits and
assignment of the dynpros can also be carried out using program
RSMODPRF. For this purpose, the program must be started without
parameters (input fields remain blank).
If required, new field exits can be created using program
RSMODPRF (see the program documentation).
Solution
1. Field exit was created with CMOD, but is not processed when calling the screen.
Since the field exit is not processed until PAI, an action must be triggered on the screen (Return, Save, ...).
Set profile parameter abap/fieldexit to YES and restart the system.
After activating the function module FIELD_EXIT... and the field exit, leave the transaction on whose screen the field exit is to be executed. The screen is not generated until the transaction is started.
Do not work on different application servers since there may be some delay before the field exit is activated.
The profile parameter must be set on all or none of the application servers.
If the field exit is to only be active on specific screens, check whether you chose the correct program and the correct screen number (take care with subscreens).
Generate the screen on which the exit should be active using SE51. It is possible that it was not correctly generated. If you want to be sure that all screens that use the data element are regenerated, you can transfer Report rsmodfdg from the correction instructions and start it with SE38. The Report uses the affected data element as the input parameter and regenerates all screens that use the data element.
Using SE51 -> Field list, check that the screen field does have a reference to a data element. In the name of the field exit, use the name of the data element and not the field name.
After transport, field exits are marked as active but will not be processed. Tip: First try deactivating the field exit once more and then activate it again.
2. How is performance affected by setting abap/fieldexit?
If a screen is generated and the profile parameter is set, a check is run on 2 tables (TDDIR, TDDIRS) to see whether a field exit must be generated for the respective field. In practice, the screen load is not generated until the screen is selected after an update. The user should not notice any difference because screen generation is very fast.
3. Can you read the contents of other screen fields in the field exit?
In principle, every field exit can store its value in the global variables of the function group (TOP) and hence make them available to other field exits. Note here that field exits are always called, not only if an entry is made in the field or if the field is empty. In addition, it is not possible to make any assumptions about the order in which the field exits will be called in the future.
4. How does the field exit behave on step loop fields ?
After the user has entered data, the field exit is called in PAI as often as there are visible fields in the step loop. The system variable SY-STEPL is incremented each time. If a new value is assigned to the field, it is displayed in the module between LOOP and ENDLOOP. This module is also called once for each visible step loop line.
5. Can field exits be debugged ?
No. Field exits must be tested separately in the ABAP/4 Development Workbench. For errors which only occur in the screen environment, it is helpful to write interesting variables to the file system using TRANSFER... . These can then be analysed there.
6. What can you do if the field contents are no longer transported to ABAP/4?
Check whether a value is assigned to the field OUTPUT.
7. When is the field exit called if a conversion exit is attached to the data element?
The field exit is called after the conversion exit. This means that the INPUT field receives the data in the same format as the ABAP/4 program receives it.
8. Although a global field exit is inactive, a function module is called which does not exist (for example FIELD_EXIT_PROGRAMM_@). This can lead to an ABAP dump error when function module FIELD_EXIT_<data element name> is called.
This is an error in the kernel which no longer occurs as of Release 3.0C. As a temporary measure, it is useful to assign a program and a screen which do not exist to the field exit and then activate the field exit.
Due to performance reasons, the active/inactive indicator is stored in the screenload. This can cause inconsistencies between Source and Load. Generate the affected screen with se51. If you want to be sure that all screens that use the data element are regenerated, you can transfer Report rsmodfdg from the correction instructions and start it with se38. The Report uses the affected data element as the input parameter and regenerates all screens that use the data element.
9. Field exit is not visible in CMOD, although created.
If you want to create a field exit for a data element, a function module is proposed with the name FIELD_EXIT_<data_element>. This function module must exist for the field exit to work. If you do not create this function module, but do create one with a suffix, the data element is not displayed in CMOD.
10. Field exit is not executed although it is active.
Fields which do not have the 'Input field' attribute usually do not trigger a field exit. The field exit is designed to allow an extended input check. It is therefore only called for input fields - even if they are not ready for input at runtime of the application by LOOP AT SCREEN.
This rule does not apply, however, if the field is located within a steploop. Here the field will be always activated, even if it is invisible.
Field exits can only be executed for fields that are directly related to the dictionary. If the relation is indirect, i.e. via an ABAP declaration (<fieldname> LIKE <dictionary element>), no field exit can be executed.
11. Field exits do not work on selection screens.
Results from the previous item since ABAP-internal fields and never the original Dictionary fields are used on selection screens.
12. Field exists do not work on check buttons.
Field exits are only intended for input fields. As check buttons count as graphical elements, you cannot install field exits on them.
13. How can all screens that use a data element be generated?
If you want to be sure that all screens that use a specific data element are regenerated, you can transfer Report rsmodfdg from the correction instructions into a customer report (e.g. zsmodfdg). The Report regenerates all screens. In this way, you can ensure that active field exits refer to screens and that inactive exits cannot be called on any screen. The Report uses the affected data element as the input parameter. The affected data element is in the name of the exit: FIELD_EXIT_<data element name>.
14. Restriction of usage
Field exit technology was developed for input fields on dynpros and cannot be used for other/new dynpro elements. This means that this technology does not offer support for the new ScreenPainter elements such as graphical elements (e.g. checkbuttons, radiobuttons, dropdown listboxes), controls (except for table controls which are supported like a step loop), or selection screens.
Erwan

Code Inspector Issue - "MODIFY - without TRANSPORTING was found in line "

Hi all
I am new to abap and my transports are unable to move further because of code inspector error
"MODIFY - without TRANSPORTING was found in line ". Help me resolve the issue.
For example
LOOP AT i_user_add.
    i_user_add-mandt = sy-mandt.
    MODIFY i_user_add.
ENDLOOP.
<removed_by_moderator>
Edited by: Julius Bussche on Oct 16, 2008 3:23 PM

Hi ,
       while modifying the internal table specify wich field you are modifying
modify <internal table > from <work area> transporting <fields>.
regards
naveen

Intrastat - Mode of Transport missing in purchase order header

We have a problem where for a supplier there is missing import data for some materials - but not others. As far as I can tell the Info Records for those with missing data are identical to those where there is no data. For example, the Incoterms field and the Mode of Transport fields are blank. The Country of Origin field on the Info Record for both of these materials is DE. Does anyone have any ideas about what may be causing this?

one more thing to check:
The mode of transport is a well used in routes. Do you use routes?
As mode of transport is header information, I doupt that item (material or article) has impact on its determination.
Here a list of tables that hold this field (EXPVZ), the tables including TVRO are tables from where your PO can get the value, the rest are tables that finally get the value from the PO.
LFM1
LFM2
T161W
T617
T618
T618K
T618T
T618U
TVRO
VEIAV
VESED
VEXAV
EIKP

Regarding field and screen exits

Hi,
     plz. send me the step-by-step procedure to create Field and Screen exit.

Screen Exits:
Screen exits are provided by SAP to allow the programmer to add his own sub screen in the already available standard SAP screen. The standard screen will have a sub screen area defined especially for this purpose. The call to this sub screen will also be present already in the standard code.
For example, there is an enhancement RVEXAKK1 available for foreign trade transactions.
As you see in the above screen in screen areas block the calling screen, its number, sub screen area and the called screen with its number are defined. Here the main screen 101 in program SAPMV86E is having a sub screen area ZUSATZ and the screen 100 from program SAPLXAKK will be the sub screen for that area.
It is mandatory for the called screen to be in a function group that starts with X. Here the function group is XAKK.
Also, if you see the above enhancement, it also has two FM exits. These two FM exits will be used to pass data to & from the sub screen. These FM calls will be in PBO & PAI modules of the main screen. These FMs are also part of the above said function group.
And the function group will not have that sub screen 100 defined. The programmer can create his own screen with the number 100(or whatever is called).
Calling of the sub screen.
sub screen call     in PBO of main screen 101          this module has the FM exit call
Sub screen call in PAI block of main screen          this module has FM exit call
Create the screen 101 in program SAPLXAKK from transaction CMOD.
Double click here to create the screen
Once screen creation is done, use the two FM exits present in the enhancement to pass data to the sub screen and get data from the sub screen.
Field Exits
1. Field exit was created with CMOD, but is not processed when calling the screen.
   o Since the field exit is not processed until PAI, an action must be
      triggered on the screen (Return, Save, ...).
   o Set profile parameter abap/fieldexit to YES and restart the
      system. Setting the profile can be done by a BASIS person.
o     To check if the parameter is set or not use transaction RZ10.
   o After activating the function module FIELD_EXIT... and the field
      exit, leave the transaction on whose screen the field exit is to
      be executed. The screen is not generated until the transaction is
      started.
   o Do not work on different application servers since there may be
      some delay before the field exit is activated.
   o The profile parameter must be set on all or none of the
      application servers.
   o If the field exit is to only be active on specific screens, check
      whether you chose the correct program and the correct screen
      number (take care with subscreens).
   o Using SE51 -> Field list, check that the screen field does have a
      reference to a data element. In the name of the field exit use the
      name of the data element and not the field name.
   o After transport, field exits are marked as active but will not be
      processed. Tip: First try deactivating the field exit once more
      and then afterwards, activate it again.

Updating table T030H with out using a transport.

Is there a way that we can open the table T030H only. We would like to give our accounting department the ability to use the tcode OBA1 with out having to have the client open. We tried allowing updates to the table T030H in our production system with out having the entire client open for updates.
We could not figure out a way to allow the tocode OBA1 to work with out having our entire client open

Hi,
Note:356483 can help you solve this issue!
The object is 'F30' in T-cd:SOBJ ->tick flag of "Current setting", select 'no transport' in transport field.
Please keep in mind that besides tran. OBA1, this flag will affect other transactions linked to this object F30. i.e. OB30,
OB40, OB53, OB89, OB00, OBBT...(they all use dialog 'RF_TABELLE_030'). In other words, you will not only open OBA1, but also other transactions mentioned here, in the production system.
Best Regards,
Gladys xing

Transportation planning status (VBUK-TRSTA) determination

Dear friends,
Can anybody explain how the "Transportation planning status" (VBUK-TRSTA) is updated in the delivery document.
As per our configuration transportation planning status is A (Not processed). But for few deliveries it is blank (Not relevant) and therefore we can't create shipment documents.
Please provide a solution for above.
Thanks,
Jeewana

Hi there,
When defining the routes, there is a field called "Rel.Transport". If you check the field, the particular field will be relevant for transport planning & you can create shipments for that route. Go to T-code 0VTC, check the notes by clicking F1 on the "Rel.Transport" field.
The VBUK-TRSTA is updated accordingly. If there is no check in the field, the table will be updated as not relevant. If shipment doc is created, it will update the status of it accordingly.
Hope this clarifies your question.
Regards,
Sivanand

Transporter Field in GR

Similar Messages

Maybe you are looking for