Encrypt some fields in an Idoc

Anyone know if it's possible to encrypt only some of the fields in an IDoc which we would like to send to an external system where they can decrypt the fields.
We will use the Basic type HRMD_A05 and the fields to encrypt is among other things personnel ID number.
Grateful for help // Peter B

i'm sorry, i'm out of my depths when it comes to abaping but i had a quick peek at service.sap.com/notes with the name of the exit you mentioned. i found note 724149 which does deal with CRM but the second part of that note seems to be appliable to the HR-system (which in this note is the source-system). have a look at it, please - it talks about manipulating IDOCs before sending them.

Similar Messages

Passing Changed extended fields using ALE-IDOC to receiving system

Hi all,
Please tell me how passing changed extended fields using ALE-IDOC to receiving system can be achieved. Is it possible by Chnage pointer concept.Do i need to do some coading after data enters into receiving system as it is required while creating the entries in database table.
For ex. in matmas05 extended for classification and inspection view and then created using 'CREATION'
related bapi.Do i also need to incorporate the changes by change related bapi or ir can be handled by change pointer concept.
Thanks.

Hi Sanu
1) Please tell me how passing changed extended fields using ALE-IDOC to receiving system can be achieved. Is it possible by Chnage pointer concept.
=> Looks like you have extended standard IDOC here. so you need to find User Exit or BADI for the Push program to populate the additional fields. Yes, it is possible thru change pointers as well.
1) Do i need to do some coading after data enters into receiving system as it is required while creating the entries in database table.
=> Yes, as suggested in 1 try finding User Exits/BADIs.
Regards
Shital

Enhanced Infotype (IT0002) field in HRMD_A07 IDoc

Hi All,
I have enhanced SAP standard infotype 0002 (via PM01) to include one new field(NWFLD1). The infotype functions perfectly well with the new field(NWFLD1).
I would now like to see this new field in the IDoc that is generated via change pointers. At present the IDoc (HRMD_A07) does not reflect the new field.
[I guess I'd need to incorporate this new field in an IDoc segment and then assign this new segment in the Tech. attributes for IT0002 and maybe also use some BADI/UserExit to transfer the values].
What steps do I need to take to achieve this?
Many Thanks in Advance.
Sanjay
PS: I have no problems with custom infotypes which work almost 'out of the box' when I create a new IDoc Segment and specify that as the 1st IDoc segment in the Tech. attributes for the custom IDoc via PM01.

Hello Sanjay,
I have a similar issue as of yours.
I had to add 2 custom fields to the standard IT0002.
I have created a new segment and attached to the extension and maitained the same in T777D.
But as of now no data is getting populated for that new segment.
I guess I also have to do some develoment but not sure where and how?
Thanks in advance for the answer.
Naveen.

Adding field in standard IDOC Segment E1EDL24

Hello Friends,
I have an urgent requirement that I have to extend IDOC segment E1EDL24 with two fields PABNR and LFSNR.
When I tries to change the segment in WE31, it shows an error message that you can only modify the segments of customer namespace and cannot modify Standard IDOC Segments.
Can we modify the standard IDOC segments, and if yes, how can we modify the standard IDOC segments. Please clarify.
Points will be rewarded generously.
Regards,
Navin

Hi Naveen,
We cannot Modify the Standard segments. But we have to Create a new Segment and Add these fields.
Then Create an Extended Idoc type
Implement User Exits in Outbound And Inbound ..
This is the Complete Steps and Info on this...with an Example...
Enhancing ALE
For example, if in an outbound interface you find that the IDOC type does not contain all the data you need to pass to the other system, you can extend the IDOC to accommodate the additional fields and enhance the ALE function modules to populate the fields. Similarly, if in an inbound interface, there is additional data that needs to be posted to the R/3 application, you can extend the IDOC type to have additional fields populated by the external system or translator or the other R/3 system and then enhance the inbound ALE function modules to post the additional data to the R/3 application.
let us use the SAP Customer Master application as an example. Specifically, letâs focus on the IDOC extension and ALE function module enhancement of IDOC type DEBMAS02 and message type DEBMAS (Customer Master) and the IDOC reduction of message type MATMAS.
IDOC EXTENSIONS
Letâs first look at the concept of IDOC extension. SAP delivers Basic IDOC types such as DEBMAS02, MATMAS02, ORDERS02, and WMMBID01. By extending the Basic IDOC type, you are actually creating a new IDOC type. You create a new segment with the additional fields. This new segment has to be associated with one of the existing Basic IDOC segments. Then you create a new extension type, which is associated with the Basic IDOC type. This results in a new IDOC type. In order for ALE function modules to relate to this new IDOC type, the IDOC type is linked to the corresponding message type.
Note that you should not add fields to existing segments but should create a new segment and associate it with an existing segment. This, in a nutshell, is the process of creating IDOC extensions.
In our example, the Basic IDOC type DEBMAS02 is used to communicate Customer Master data to the SAP Customer Master application. Even though the application has a screen to enter and store a contact personâs business address (see Figure 1), DEBMAS02 does not have a segment or fields that communicate the contact personâs business address. If your business requires that this business address be communicated to the other system through the ALE interface for Customer Master, then you have to extend the DEBMAS02 IDOC type, and enhance the corresponding ALE function module.
In DEBMAS02 the contact person fields are present in segment E1KNVKM and the business address of the contact person is stored on the SADR SAP table. You need to create a new segment, Z1SADRX, that is associated with E1KNVKM. This will be done in the process of creating an extension type ZDEBMASX. This extension type will then be associated with a new IDOC type, ZDEBMASZ. IDOC type ZDEBMASZ will be linked to message type DEBMAS for Customer Master. The final step in the IDOC extension process is to check the new objects. This check also verifies the structural integrity of the IDOC type. Letâs look at each of these steps in more detail.
1. Create an Extension Type and a New Segment.
Determine the fields on table SADR that you are going to provide for in the new segment Z1SADRX. You need fields for name, street, city, region, and country to give the business address of the contact person. You also need fields for the address number. ADRNR is a field in SAP tables such as SADR that uniquely identifies the address of an entity. This field is cross-referenced from other tables to the SADR table to obtain the full description of the address. Because this is an IDOC type for master data, the first field of the new segment will be MSGFN. The message function field informs the receiving system of the action to be taken for that particular segment. In the code that you write for populating the new segment, the value of the message function is the same as that of the parent segment E1KNVKM. In all, you will have 12 fields in segment Z1SADRX (see Table 1).
To create an extension type and new segment:
Use transaction WE30 or from WEDI go to Development -> IDOC types.
Enter ZDEBMASX for Object Name.
Choose Extension Type.
Click on Create.
You will see a pop-up screen. Choose Create New, and enter a description. For version 4.x, enter DEBMAS02 in the Linked Basic Type field. Enter.
You will see a screen with ZDEBMASX and its description in the first line. Click on this line, and press Create. For version 4.x, expand the tree of segments, and place the cursor on E1KNVKM.
You will see a pop-up screen. Enter E1KNVKM as the reference segment. Enter.
For 4.x, press Create after placing the cursor on segment E1KNVKM.
You will see a line appear with E1KNVKM hierarchically below ZDEBMASX, with a description "Customer Master contact person (KNVK)."
Click on this line and press Create. You will receive a message indicating that the new segment being created will be a child segment of E1KNVKM. Enter. A pop-up box appears for the new segment.
Enter Z1SADRX as the segment type, 1 for Minimum, 1 for Maximum. Leave Mandatory segment unchecked. These entries imply that there is only one Z1SADRX segment for every occurrence of the E1KNVKM segment, and also that this segment is not mandatory. Note that if the parent segment is not mandatory, then the child segment should not be mandatory, because this could result in a syntax error during the creation or processing of the IDOC.
For 4.x, you must first create the IDOC segment Z1SADRX (Iâll explain why in a moment) from the menu path WEDI -> IDOC -> Development -> IDOC Segment.
Click on Segment Editor.
On the next screen, click on Create.
Enter a development class for the object. Enter.
This will take you to the screen for segment definition. Enter a description for the segment. Enter the field name, data element, and the data element documentation name. In most cases, all three fields may have the same values. If you are using a field in the segment that is not present in the ABAP/4 data dictionary, you must first create the domain, data element, field, and appropriate documentation before using it in the new segment.
Enter these three columns for all 12 fields. Save.
Click on Generate/Activate, F3 to step back.
From screen Maintain Segment, go to Segment Type -> Release. A checkbox now appears beside the segment definition Z1SADRX (see Figure 2). Check this box. Save.
Save again to store the descriptions of the segment, F3 to step back.
Save the extension type.
It is possible to have several new segments with relevant Basic IDOC type parent segments in a single extension type. However, you can form only one IDOC type based on a single extension type.
2. Create an IDOC Type.
The next step is to create an IDOC type by associating the extension type that you created with the Basic IDOC type. This is a simple process:
From transaction WE30 or WEDI go to Development -> IDOC Types.
Enter ZDEBMASZ for Object Name.
Click on IDOC Type.
Click on Create.
Enter DEBMAS02 for Basic IDOC type.
Enter ZDEBMASX for extension type.
Enter a description.
Enter.
You will see a display of the composite IDOC type with all segments, including Z1SADRX (see Figure 3).
It is possible to associate only one extension type with a Basic IDOC type for a given IDOC type. However, you can have multiple new segments in an extension type.
3. Link IDOC Type to Message Type.
The next step is to link the new IDOC type to its corresponding message type. This is important, because this relationship is referenced in the partner profile parameters where you specify the message type and IDOC type to be used for that particular representative system. To link the message type:
Use transaction WE82, or from WE30, go to Environment -> IDOC Type / Message Type, or from WEDI go to Development -> IDOC Type -> Environment Î IDOC Type / Message Type.
Click on Display <-> Change.
Click on New Entries.
Enter DEBMAS for message type.
Enter DEBMAS02 for Basic IDOC type.
Enter ZDEBMASX for extension type.
Enter your SAP R/3 release number for Release.
Save.
This data is stored on the EDIMSG table and is accessed by several ALE processes to relate the message type to the IDOC type.
4. Check the IDOC Type.
Before checking the IDOC type for consistency, it is important to perform another step that releases the extension type to the IDOC type:
From WEDI go to Development -> IDOC Types -> Extras -> Release Type, or from transaction WE30 go to Extras -> Release Type.
For the Object Name ZDEBMASX and radio button Extension Type, click Yes.
The extension type has now been "released."
You canât edit the extension type once itâs released. To cancel the release for further editing or deactivation, go to WE30 Î Extras Î Cancel release. The final step in the IDOC extension process is checking the validity of the IDOC type:
From transaction WE30 or WEDI go to Development -> IDOC types.
Enter ZDEBMASX for Object name.
Click on Extension Type.
From the Development Object menu select Check.
Repeat the operation for IDOC type ZDEBMASZ.
A check log will be generated for each run with details of correctness or errors (see Figure 4).
In some situations it is possible to receive errors during the check process, especially segment length errors. The incorrect IDOC segment can be repaired and corrected by executing program RSEREPSG. This program checks the formal consistency and repairs incorrect segments. In test mode it will generate a log of formal correctness for the specified segment only. For the program to repair segments in normal mode, the underlying IDOC structures (DDIC structures) must be active. This program rectifies the lengths of the DDIC structures and not the fields themselves. RSEREPSG can also be used to change the person responsible for the object and the release flag.
Menu paths may vary slightly depending on the release/version of SAP R/3, but the procedures and the principles are the same.
ALE FUNCTION MODULE ENHANCEMENTS
Having extended the IDOC type to contain additional fields for an inbound or outbound application, you now want to enhance ALE function modules for populating the additional segment on the outbound or applying the additional segment data on the inbound application.
The core working code for ALE processes for a given application area is always encapsulated in ABAP/4 function modules. These function modules are associated with such control information as message types and process codes. So the ALE process checks this control information and derives the name of the function module to invoke for that particular IDOC processing from certain database tables. These function modules contain objects known as customer functions, which can be considered SAP Enhanced user exits. A function module is called at a particular point during the processing of the main program or function module, and it can be used to influence data processing at that point by adding code to the customer function. The customer function behaves like a normal function module and has import and export parameters, tables (internal tables) statement, and exception processing. Unlike a conventional user exit, customer functions give you the ability to modify only data available to you by the function moduleâs parameters and internal tables. While most ALE/EDI function modules are supported by customer functions, there are ALE/EDI processes that still use conventional user exits. There are a few ways to determine which function module to enhance for a given message type/process code:
For master data distribution, from SALE go to Extensions -> Master data distribution -> Setup additional data for message types. Search for message type DEBMAS in this example. You see an entry for DEBMAS associated with function module MASTERIDOC_CREATE_SMD_DEBMAS. This data is stored on table TBDME. The function module names for all master data message types follow this pattern: MASTERIDOC_CREATE_SMD_messagetype. This function module calls another function module of name MASTERIDOC_CREATE_DEBMAS or MASTERIDOC_CREATE_messagetype. Search for the words customer function, and you find several hits that can be used to add code to the function module.
From WEDI got to Control -> Inbound process codes -> Inbound with ALE service -> Processing by function module (transaction WE42), or from WEDI go to Control -> Outbound process codes -> Outbound with ALE service -> With function module (transaction WE41). There will be function modules associated with the process codes. For inbound, the function modules usually follow this pattern: IDOC_INPUT_messagetype: for example, IDOC_INPUT_CHRMAS for inbound characteristics master.
Use transaction WE57 or from WEDI go to Development -> Message/Application Object. The entries list the function module, Business Object, message type, and IDOC type that are used for inbound ALE/EDI interfaces.
Customer functions are not specific only to ALE and EDI but also to all programs/modules in SAP R/3. Customer function is a SAP enhancement component; the other two types are menu and screen enhancements.
All customer function exits are maintained in SAP enhancements and are found by using transaction SMOD. After executing transaction SMOD, pull down (F4) on the enhancement name field, and execute again. This provides you with a list of all SAP enhancements available. SAP enhancements are grouped by development class pertaining to an application area. Choose Application development R/3 SD master data distribution for development class VSV to lead to a screen that lists VSV00001 as an enhancement (see Figure 5). Press Component +/- to display its function exit components. There are four possible components listed, all of which are function exits (and are function modules) that are called from the ALE function modules in the form Call Customer Function Î001â. This is a special occurrence of the ABAP statement Call. Go to item Exit_SAPLVV01_ 001, which you need to enhance for the Customer Master outbound example of an IDOC extension. In the ALE-function module MASTERIDOC_CREATE_DEBMAS, the statement CALL Customer Function 001 is translated in the background to call component EXIT_SAPLVV01_001. Although this function exit can be edited using transaction SE37, you will use a simpler approach.
When you use SAP enhancements and their components, you manage them with an SAP object known as a project, which is like an envelope containing the selected enhancements and their components. A project can be used to control the execution of components and to transport them to other clients and instances in SAP. Basically, the process involves creating a project, including enhancements and components that are to be enhanced, editing the components, and then activating the project. The following process creates a project for our example Customer Master IDOC extension:
Execute transaction CMOD.
Enter name of project, say CSTMAST1.
Click on Create.
Enter a description of the project.
Save.
Click on SAP Enhancements.
Enter VSV00001 for Enhancement.
Save.
Once youâve created the project, edit the function exit components and activate the project. Remember that the code in the function exit enhancement will execute only if the project is activated. In fact, this is a convenient SAP enhancements feature, whereby the work in progress (developing code in the customer function) will not affect users of that application. When the code is completed, the project can be activated so the enhanced functionality takes effect. It can also be deactivated for maintenance.
As mentioned earlier, customer functions (function exits) are embedded in ALE function modules and can be used to influence the creation and modification of IDOC data on an outbound application or to post additional or modified IDOC data to an inbound R/3 application. Function exits are similar to regular function modules, with import/export parameters, tables (internal tables), and exceptions.
The two important factors to consider while developing the customer function are:
1. The point in the ALE function module where the function exit occurs
2. The data made available by the customer function that can be modified or posted to the R/3 application, based on the direction.
Because some function modules have several customer functions, it is critical to choose the function exit best suited for that particular enhancement. Do not attempt to perform activities that the function exit is not designed for. The importance of this point is illustrated by the following description of enhancing function modules for outbound and inbound ALE interfaces.
Outbound interfaces. In an outbound ALE interface you use function exits (customer functions) to populate additional segments created by an IDOC extension or to modify the existing IDOC data segments as per business requirements. Previously, you identified that enhancement VSV00001 has a component EXIT_SAPLVV01_001 (function exit), which can be used for populating the additional data segment Z1SADRX that you created in the IDOC extension ZDEBMASX (IDOC type ZDEBMASZ, based on Basic IDOC type DEBMAS02). You also learned that the ALE function module that calls this function exit is MASTERIDOC_CREATE_DEBMAS, which has a statement Call Customer Function 001.
Browse the function module MASTERIDOC_CREATE_DEBMAS using transaction SE37. You will find that this customer function is invoked for every segment of IDOC type DEBMAS02. In fact, the function exit is called soon after the creation of an existing segment has been populated with data and appended to the IDOC data table (internal table). Also, the function exit is exporting the message type, IDOC type, and the segment name and is importing the IDOC extension type. It is also passing the IDOC data internal table. This indicates that the ALE function module is allowing you to populate additional segments for every existing segment and modify the existing segmentâs data.
Letâs write ABAP/4 code to accomplish the task of populating IDOC segment Z1SADRX with a contact personâs business address:
From SE37, display function module MASTERIDOC_CREATE_ DEBMAS.
Find Customer Function 001.
Double-click on 001.
The function EXIT_SAPLVV01_001 will be displayed.
Double-click on INCLUDE ZXVSVU01.
You will be asked to create a new include object. Proceed as desired.
Enter code (as in Listing 1).
Be sure to perform a main program check (Function Module -> Check -> main program) and extended program check (Function module -> Check -> Extended check).
Now that you have extended the IDOC and enhanced the ALE function module based on the requirements for the contact personâs business address on the Customer Master, letâs test the interface. You should create a logical system and define a port for this interface. You should also configure the Customer Distribution Model to indicate that message type DEBMAS is being distributed to this logical system. The only difference in configuration between a regular outbound ALE interface and an enhanced one is the partner profile definition. While maintaining the outbound parameters of the partner profile, make sure the IDOC type is ZDEBMASZ. The fields for Basic IDOC type and extension type are automatically populated with DEBMAS02 and ZDEBMASX, respectively.
To maintain the contact personâs business address of a customer:
Use transaction BD12 or from BALE go to Master Data ->Customer -> Send and send that Customer Master record by executing the transaction after filling in the relevant fields such as customer number, message type, and logical system.
Use transaction WE02 or WE05 to verify the IDOC created. You should see the new segment Z1SADRX populated with the correct data.
With SAP releases below 4.5B, you cannot capture changes to business address through change pointers because a change document object is not available for capturing business address changes, and also earlier releases have not been configured to write change documents for a contact personâs business address. If you would like this functionality, you can either create change document objects, generate function modules to create change documents, and perform ALE configuration to tie it in, or make a cosmetic change to the contact person screen data while changing the contact personâs business address so that it gets captured as a change to the Customer Master. Subsequently, the ALE enhancement that you performed captures the contact personâs business address.
Inbound interfaces. The process for enhancing inbound ALE interfaces is similar for outbound, with a few exceptions; specifically in the coding of customer functions (function exits) for the ALE/EDI function modules.
The first step is to create an IDOC extension for the specific Basic IDOC type by adding new segments at the appropriate hierarchy level: that is, associated to the relevant existing segment. Populate the data fields on the new segments with application data by the translator or external system/program before importing them into the R/3 System. Then, find the ALE function module that is invoked by the inbound processing. By browsing through the code or reading the documentation on the function exit enhancements using the SMOD transaction, identify the function exit in which you should place your code. The technique used in the code to post the additional or modified IDOC data to the application can vary based on the application rules and requirements, the data available at that point in processing, and the application function modules available to update the application tables. It is important to search first for application modules that process the data and see if they can be called within the function exit. If the additional data in the extended segments in specific to a custom table or resides in nonkey fields of a single or small set of tables, you may be able to update it directly by SQL statements in the function exit. This approach should be carefully evaluated and is certainly not highly recommended.
Another option is to use Call Transaction from within the function exit to process the additional data. For example, in the case of message type WMMBXY for inbound goods movements from a warehouse management system, the standard interface creates batches for materials, but does not update its characteristics. In such a case, you can use Call Transaction MSC1 to create the batch and assign characteristic values to it from within the function exit provided.
Error handling is a very important consideration when making enhancements to inbound ALE/EDI objects. In ALE and EDI inbound processing, workflow is used for handling errors at different levels such as technical and application. If workflow has been configured for the interface, the error messages and workflow items flow to the inbox of the named recipient(s).
It is also critical to enhance the workflow that handles notifications of the inbound ALE/EDI process. In most scenarios this is not a very difficult task because SAP lets you influence the workflow parameters and messages in function exits (customer functions). You typically do this using flags and message codes to trigger certain workflow actions. If you conform to the status codes and flags stipulated for workflow processing, the enhancement could be error-free and seamless. In the case of an inbound IDOC with an extension, you should populate the EDIDC fields IDOCTYP (new IDOC type) and CIMTYP (extension type) accordingly.
Reward if Helpful

Need billing text field name for IDoc mapping

Hi Friends,
our users use CRM web application to send orders to SAP via IDocs. They want to have billing text (In German it is called Rechnungstext or Faktura text) so that they can enter some text here if they want to enter something. My question is, what is the field name and IDoc segment for billing text? We need this information to map in XI.
Br, Sats.

The solution is:
The standard Idoc text segment can be used for the text in sales order. From SD side the text types have to be customized. This is necessary for the XI mapping.
Regards,
Sats.

How should i remove the filed of e1p0041 segment field from generated idoc

Hi Experts ,
       I have a requirement , whenever an idoc is generated for the particular segment(e1p0041 ) all the fields of infotype should be
in generated segment , but there is no need of some field like dat01, dat02, in e1p0041 segment .
     but it is only do programmatically .
    Please give an help .
thanks in advance.
Venkat

Hello Raju
Thank you for your reply.
Unfortunattely the Field tab doesn't have the Appearance in it.
The field tab contain only the following Items:
Type : Image Field
Caption:
URL
Embed Image Data
Sizing: Scale Image Proportionally
Presence: Visible
Locale: Default locale
There is no item named "Appearance".
I am using AdobeLiveCycle Designer 8.0
Version 8.01.3250.1.491864
Regards
dstj

Additional fields for InternalOrder IDOC

Hello,
We try to distribute internal orders with ALE to several clients. The distribution of the internal order IDOC works fine with "InternalOrder.SaveReplica".
Here the problem: We have some additional fields which should be attached to every IDOC. Unfortunately we don't know how to add the additional fields to this IDOC type. It doesn't work the same way as for other IDOC Types (WE30 and WE31) because the Internal Order IDOC is a generated IDOC type.
Is there someone who can give us some help?
Best regards
Stefan Blaser

Hi,
What do you mean by ?
The problem is the Zsegment is not visible with in exit EXIT_SAPLEINM_002.
You will have to write the code in exit to populate the segment and add it in the Idoc.
Check in SE11 if the dictionary structure created for the segment is active. Also, if the segment is released in WE31.
KR Jaideep,

Fields included in IDOCS

Hi Experts,
I need to identify what fields are located on idocs being sent to the bank and, How do I locate the IDOC file being sent to the bank besides using BD87? The most important task I have is to locate the fields being issued on the IDOC.
Any help is much appreciated!!

Hello,
You can display the IDOC data in t-code WE02. This only displays the list of field that are populated with some data.
For IDOC file, it depends on how your system is set up. If you are using any middleware like PI / XI, then IDOC would first go to PI and then to bank. So, you can ask your PI folks for the file. If the IDOC is directly sent to bank, then you can check with bank. If you are sending fiel as XML, then you can find the file in your system itself.
If you want to know the field mapping logic, you have to check the requirement documents. Most of the fields are populated by standard SAP by default unless there are some customer specific requirements.
Thanks,
V V

Multiprovider is not capturing some fields data

Hi Friends,
               I got a proble when iam working on multiprovider,where i have taken two cubes into that multiprovider,now the problem is when i execute a report on muliprovider some fields are not populating with data.
{{cube are :billing cube(data sources:2lis_11_vaitm&2lis_13_vditm)
              account receivable item data(0fi_ar_4)}}
                       As this is RRI sender query having both cubes information,when i execute report when ever report captures first cube report the second cube data is not capturing vice versa.
Thanks and Regards
Gunasekhar

Could be a problem on identification (setting on multiprovider).
Try to execute on transaction RSRT your query
execute + debug
on debug option set "Multiprovider explain"
and report the log in this post.

Hiding some fields from ALV report

Hi All,
I want to know if there is way to hide certain fields in ALV for some users only and not for others?
If I use the option NO_OUT = 'X' it will not be displayed in the list but the user can see the in the Layout option fields but if use NO_OUT = 'X' and TECH = 'X' the field will not be in the list and in the layout also but other users will miss that field.
If I create user specific variant, but once the user is in the report he can change the layout so certain fields cannot be hidden.
So, is there any way to hide some fields for certain users and not for others without hard coding user ids in program and restricting the fields from display??
Thanks in Advance.
Sonali.

Thank You Vijay for the reply.
I knew that Authorization object was the final solution but before using it I wanted to find out if there was a way in the ALV report to restrict certain fields.
Sonali.

Background job on change of some field!!

HI
i have to trigger a background job on change of some field value (status field chages it's values from w to U).
so how to go about the same..
how to call a background job once some fields changes!!
regards
Gunjan

1. You can use JOB FM's to invoke the job.
2. You can call the FM ( Background execution program ) in background.
CALL FUNTION .... IN BACKGROUND.
Regds
Manohar

How can i transfer some fields from one table to another using a trigger

hi,
i have two tables;sales and accounts.i want in my accounts form to enter salesid which is then validated and if it exists in the sales table, some fields are copied to the accounts table automatically.how do i go about this.thanx

hi,
the code u gave me is not running.let me explain in
detail.i have two tables;sales and accounts in my
database (oracle 9i).each have a corresponding form
in the developer window.these tables are linked using
saleid.this id is entered and saved in the
database.when the person is paying in the cash
office,the saleid on an invoice form is entered on
the accounts form.it is supposed to search the sales
table and if the ids match,some records are extracted
from the sales table to the accounts form instead of
the accounts clerk entering the details all over
again.these details will be used to generate a
receipt an then the record on the accounts form is
saved to the database.the contents of the two tables
are:
sales(saleid(pk),startno,endno,quantity,amount,saledat
e)
accounts(receiptno(pk),saleid,startno,endno,quantity,a
mount).
please advice and thanks very muchWhat does it mean "not running" ?
Sure, it is running.
Did you tested my example ?
And it does exactly what you need.
You didn't provided table structures and insert statements,
that's why i showed you the method on 2 emp- tables.
But it is exactly, what do you need.
Change my emp_1 on your sales,
and my emp_2 on your accounts,
and compare the results.
If you cannot directly copy and paste
and say to your teacher / chief "My homework / task is ready"
it doesn't mean, that the solution didn't provided ...

How to find out the manditary fields in an IDOC

Hi,
How to find out the manditary fields in an IDOC.
For example MATMAS05 .
For this 2 segments I want to find out the manditary fields.
E1MARA
E1MAKTM

Hi,
go to transaction WE30 and give the corresponding IDoc type and enter. Then you will get all segments for that IDoc type then double click on segment. A popup box will come in that it will show a check box whether it is a mandatory segment or not. And segment editor button will give all the field details.
Regards

Make the output of the BI report rtf file some fields non editable

Hello All,
I want to make some fields in the output of the BI report as editable and some non editable. Any output format is fine (PDF, RTF or HTML) Please let me know if anyone knows how to do it.
Thanks in advance..
Anu

You can add RTF to active allowed output type list (provided that your reporting system supports it) by going to CustomerReportExtensions.xml file and adding the following node right after ParameterTypes node:
<ActiveReportOutputTypes configChildKey="key">
<ActiveReportOutputType key="RTF" value="RTF" extension=".rtf"/>
</ActiveReportOutputTypes>

Help: what meaning of some fields in INSTALL [for install] fields ?

Hi all,
I don't understand some fields in Data field of INSTALL [for install] command.
There is section *"A.1.1.4.2.1 -     Toolkit Applet Specific Parameters "* of specification +3GPP TS 23.048 V5.9.0+
*Presence         Length          Name*
Mandatory         1                  Length of Access Domain field
Mandatory         1-p          Access Domain (see A.1.1.4.2.3)
Mandatory         1                  Priority level of the Toolkit applet instance (see A.1.1.4.2.4)
Mandatory         1                  Maximum number of timers allowed for this applet instance
Mandatory         1                  Maximum text length for a menu entry
Mandatory         1                  Maximum number of menu entries allowed for this applet instance
Conditional                /     Position of the first menu entry ('00' means last position)
Conditional               |          Identifier of the first menu entry ('00' means don't care)
Conditional
                           |     ….
Conditional               |          Position of the last menu entry ('00' means last position)
Conditional                \     Identifier of the last menu entry ('00' means don't care)
Optional         1                  Maximum number of channels for this applet instance
Optional         1                  Length of Minimum Security Level field
Conditional     0-q          Minimum Security Level (MSL) (see A.1.1.4.2.5)and more description like this:
The position of the new menu entries is an absolute position among the existing ones.
A part of the item identifier shall be under the control of the card system and the other
part under the control of the card issuer. Item identifiers are split in two ranges:
-     [1,127] under control of the card issuer;
-     [128,255] under the control of the toolkit framework.
If the requested item identifier is already allocated, or in the range [128,255], then the
card shall reject the install command. If the requested item identifier is '00', the card shall
take the first free value in the range [128,255].These pair fields *"Position of the first menu entry ('00' means last position)"* and
*"Identifier of the first menu entry ('00' means don't care)"*.
What purpose do these fields describe? Let give some example for me!
Thanks,
HoaND
Edited by: hoaibaotre on Oct 27, 2011 10:21 AM

You give us no clue about what you used to record/playback scripts

Encrypt some fields in an Idoc

Similar Messages

Maybe you are looking for