XD01 Customer data Additional Screen

Hi,
I have created a BADI implementation for XD01/02/03 to add custom screen with additional customer fields using BADI CUSTOMER_ADD_DATA and CUSTOMER_ADD_DATA_CS. Works well, customer master now has a new button that brings me to a screen I defined.
Now I have a requirement to only show this additional screen button for certain Sales Area and I cannot find a way to do it.
I can hide tabs on custom screen by Sales Organization, but activating whole button+screen functionality looks to only be possible before Sales Area data is known during IF_EX_CUSTOMER_ADD_DATA~CHECK_ADD_ON_ACTIVE
Is there something I am missing?
Jurijs

Hi Jurijs,
Have you checked the method 'SUPPRESS_TAXI_TABSTRIPS' for the BADI definition 'CUSTOMER_ADD_DATA_CS'? It looks like maybe you can use this to suppress the tabs based on your sales area requirement.
Regards,
Ryan Crosby

Similar Messages

Screen exit in SAPMF02D screen number 7000 (xd01) customer master

Hi friends,
i need to add one custom field in customer master(xd01) screen number 7000. is there any screen exits for that? or how can we add a custom field in screen?. plz tell me the steps for that. The additional field which i have to add is, comes under sales area data Tab - billing document tab - billing document.
Message was edited by:
venkata kumar

with in same condition i m facing the same problem if you already have any sollution plz suggest me.
waiting for your kind reply

Addional customer data extension in the screen

As u know there are 10 fields in Customer master (addional customer data-central).
Need to add some more values to the screen by including customs fields to kna1.
But how can i make those displayed in the screen?

Apart from adding the additional customer fields in the Include structure of the KNA1 table, further settings has to be done in SPRO.
For example, to add a field KNA1-STCD3 (Tax Code 3) to TCODE XD01,XD02.
SPRO
financial accounting -> Accounts Receivable and Accounts Payable ->
Customer Accounts -> Master Data -> Preparations for Creating Customer
Master Data -> Define Account Groups with Screen Layout (Customers)
select your account group
In the Field status screen, double click on General data
Then double click on Control
Activate Tax number 3
select Change customer (Centrally)

Adding new fields to additional data B screen in sales transaction

Hi All,
I have a requirement like this I need to add 3 input fields and 1 push button(select oppurtunity) in additional data B screen of sales order transaction.If I click on this button I want geneate one pop up dialog box just like as search help box and I should be able to search data for these 3 fields data based on some 4 input fields data?How can I acheive this?I can add button and what I have to write the code in PBO and PAI of this screen?Please some body help me in this regard.
Regards
Mahesh

Hi friend,
In SAP we can add few fields from maintain reserve fields. Please go through it;
Maintain Reserve Fields In Customer Master
There are reserve fields in the customer master record which are not used in the standard system. They are available for use and are as follows:
Customer group 1 (View: V_TVV1 Field:KVGR1)
Customer group 2 (View: V_TVV2 Field:KVGR2)
Customer group 3 (View: V_TVV3 Field:KVGR3)
Customer group 4 (View: V_TVV4 Field:KVGR4)
Customer group 5 (View: V_TVV5 Field:KVGR5)
You can find the fields in the customer master record under the sales and distribution data in Sales. Choose additional data under Environment.
It is advisable to change the field description (Data elements KVGR1 to KVGR5).
This is described in the system modifications in the Reserve fields unit of the customer master record:
Reserve Fields in Customer Master
Record
In this step you maintain the valid entries for the individual views.

Change labels Additional Customer Data

Hi Expert Forum
In the transaccion XD02 -> in the option "Additional Customer Data (Central)" I want to change the label "Attribute 1" for a new value for example "Customer Group"
How can I do this?
Program name     SAPLV02Z
Screen number    0100
Program name     SAPLV02Z
Status           A001
Transparent tabl KNA1
Field name       KATR1
Data element     KATR1
DE supplement    0
Screen field     KNA1-KATR1

Goto CMOD->Text enhancements->Keywords->Change->Enter Data element and change the text.
Thanks,
SKJ

Change label "Attribute1" in the standard dynpro "Additional Customer Data"

Hi Gurus,
I have a requirement to change the field label "Attribute 1" in the standard dynpro "Additional Customer Data". This dynpro is in "Customer: General data" (xd01, xd02, xd03), menu option "Extras" ,
"Addtional Data".
Nobody knows, is it possible customazing?
Thanks in advance,
XeviG.

Hi Suma,
I try change the name of the field table but I could not do it.
Please, could you me explain the process? I don't know if I did do the change correctly.
Thanks in advance.
XeviG.

Pass data between customer master enhancement screen ALV and BADI

Hello
I currently have my custom screen on customer master working. I have an ALV that I display on the custom tab that I created on customer master. It's an editable ALV so the user can change values on it and then when they hit "Save" on the customer master I need to have these values transferred over to an external system using an RFC-JCO communication. I got all of this to work but I still don't know how to pass values from my ALV screen to the GET_DATA method of CUSTOMER_ADD_DATA_CS BADI or for that matter any methods of the BADIs involved.
Right now to pass values from the BADI to my custom screen I simply use SET PARAMETER/GET PARAMETER combinations but I cannot keep using that when I have over 1000 values to pass over.
I looking for this so that I can perform some data validations on my ALV fields when the user hits enter after typing the values. Also, to check whether anything was changed or not - to set or not to set the 'fields changed' flag in the BADI, etc.
Any help would be appreciated. Will award points for useful info.
Thanks,
Kushal

Are these details not available on the Std. Customer Screen ?
Or you want some additional data. BTW in the method GET_TAXI_SCREEN you won't find access to the Customer data. For this you have to implement the method(s) GET_DATA and/or SET_DATA.
BR,
Suhas

Insert customized input field in BP Organization addition screen(BUP110)

Hi experts,
Inside bp transaction when ever I am trying to add Organization, inside Name section(BUP010) one customized input field I want to add. What are all the procedure I need to follow in BUPT transaction to add new input fiels in the name section? How to map field group, view, section and screen? How to display that field on the name section of that Organization addition screen?

Could you please tell us how you fix it? It would be helpful for the rest of the community.
Greetings,
Blag.

How to create Customer data TAB in PO -ME23N

Can anyone tell me how to add 'Customer data' TAB in the PO heade TABSTRIP. I have to add it in the header besides 'Status' TAB.
I know an enhancement 'MM06E005' which is used for this purpose.
Thanks
SMS

Hi
see this sample doc and do it accordingly
by creating a project in CMOD and assigning the Enhancment MM06E005 and writing the code in the respective screen
How to implement screen exit for a SAP standard transaction
Introduction
SAP provides standard transactions to enter data into database. But a client may want to maintain some additional information in SAP other than what is provided.
To make provisions for this, additional screens have to be provided and additional fields must be added into appropriate database table.
To pave way for this, SAP has provided the option for screen exits. Usually, SAP provides the following:
An append structure in the database table with the new fields.
A subscreen area into the standard screen where the programmer can attach his subscreen of his own program with the new fields.
A function group under which the new subscreen has to be created with the new fields.
Function exits to synchronize the PBO and PAI of the standard SAP program with the PBO and PAI of the subscreen so that data can flow back and forth between the standard SAP program and the program written by the developer for the subscreen. These function modules also exist in the same function group under which the subscreen will have to be developed.
Finally, a linkage has to be done between the subscreen area of standard SAP screen with the custom subscreen constructed by the developer.
Typically, SAP provides an enhancement in which the developer can create an append structure, use the function exits to synchronize the PBO and PAI of the standard SAP program and the custom subscreen program, and make the necessary linking( as mentioned above in step 4. But, again, this is not a hard and fast rule. Linking in some case, is also done by configurations.) SAP also usually provides the name of the function group under which the subscreen has to be developed.
Necessary guidance about implementing a screen exit development is usually available in the Documentation section of the enhancement ( can be availed by transaction SMOD).
Pre-Requisites
The developer to work on screen exit should have essential knowledge on the following:
DDIC concepts, including the knowledge of append structure.
Concept of SAP Enhancements and implementing them using Projects.
Concept of function exits.
Knowledge on Module Pool including subscreens, Tabstrip controls etc.
Steps
Guidelines
So, a developer can follow the guidelines mentioned below to implement a screen exit to a standard SAP transaction, as and when required:
Find out the Required Enhancements
Go to SMOD. Press F4 in the Enhancement field. In the next popup window, click pushbutton SAP Applications. A list will appear that contains information on all the enhancements, categorized under functional areas. Developer must search for the enhancements relevant to his functional area of interest for e.g., Purchasing, Asset Accounting, etc.
Note down the enhancements. Then, come to the initial screen of SMOD and view the documentation of each enhancement to find out which one is required for your development.
Utilize the Enhancement in a Project
After you have found one, do as directed in the documentation. Generally, the steps are as follows:
Create a project using CMOD including your enhancement.
Create the append structure with new fields.
Go to the desired function group and create a subscreen with the new fields. Write PBO and PAI for the subscreen, if required.
Use the function exits in the enhancement to link the PBO and PAI of the subscreen with that of the main SAP program supporting the SAP transaction.
Maintain necessary linkage between the subscreen area of standard SAP program with the custom subscreen developed along with the custom program name. This can be done in the project (developed by CMOD including the enhancement) or outside as a part of configuration.
Activate the project.
Test to ensure that required functionality are met.
Case Study 1
Add three new custom fields for Asset master and maintain information for them
Requirement
Three fields in the legacy system have to be maintained in Asset master. These fields are:
Original Asset number 20 characters
Location 2 15 Characters.
Model no 20 characters
Location 2 should start with L.
Pre-Analysis
Finding out the Enhancement
As described above, the enhancement is determined. It was found, that enhancement AIST0002 will serve the purpose. It contains the following components (can be viewed by transaction SMOD):
Exit Type Description EXIT_SAPL1022_001 Function Exit Check of User-Defined Fields when Using Create and Change BAPI EXIT_SAPLAIST_002 Function Exit Transfer Data for User Subscreens in PBO. EXIT_SAPLAIST_003 Function Exit Transfer of User-Defined Fields to SAP Master Data Transactions CI_ANLU Customizing Include Include structure to add new fields
Studying the Function Exits
The function module level documentation for the function exits are then viewed from transaction SE37. The documentation clearly laid out for the purpose for their use:
EXIT_SAPLAIST_002
Function module Level Documentation
This function module is called by asset master data maintenance at the start of the dialog. (When changing, it is called after reading of the data from the database; when creating it is called after the transfer of the default values from the asset class and reference asset.) The purpose of the function module is to enable this function group to recognize the master data. For interpreting or controlling master data fields that are important for user fields, it is possible to transfer to global variables at this point, so that they can be recognized when the user subscreens are processed.
Import Parameters
Understanding
This function module is called at the PBO to pass the information retrieved from the database to pass them to the custom subscreen and its underlying program. Import parameter : I_ANLU will be populated with the values for user-defined fields which will be passed to the subscreen program. So, there must be some sort of variable assignment from I_ANLU.
EXIT_SAPLAIST_003
Function module Documentation: This function module is called by SAP asset master data maintenance after the screens are processed, but before saving. The purpose of the function module is to transfer fields entered on user sub-screens of SAP asset data maintenance to the database for updating. The export parameter for this function module is:
Understanding
This function module will be used to transfer the user entered data in the subscreen fields to the main SAP program, which will then be saved into the database.
Studying the Documentation of the Enhancement
The enhancement documentation (as is viewed from the initial screen of SMOD] also supports the idea. Moreover, it informs that we need to develop a subscreen under function group XAIS. This is the function group under which the two function exit modules also exist. So, if the custom subscreen refers to the global data of the function group XAIS, then those values will also be available to these function exits as well.
Going to SE80 and viewing the function group XAIS helps us to inform that there are three DDIC tables declared for it:
Deciding the Final course of Action
After making all the investigations, the final course of action was determined.
SrlNo Step Justification
A project has to be created using transaction CMOD where the enhancement AIST0002 will be included.
Customizing include CI_ANLU has to be created with the custom fields demanded When CI_ANLU will be developed, the custom fields will get appended to the database table ANLU. Also, these fields will be used to create screen fields in the new subscreen.
A custom subscreen, say, 9000 will be developed under function group XAIS. The screen group for the screen will be CUST (or any name). The three custom fields added to table ANLU (by creating CI_ANLU) will be used to create new fields in the screen.
In the PAI of the subscreen, validation for Location to start with L will be added. The subscreen with three new fields has to be developed so that it can be attached to a subscreen area of the asset master screens.
In the custom include of the function exit module EXIT_SAPLAIST_002, the following code will be written:-
ANLU = I_ANLU. I_ANLU is the import parameter of this FM. The value is assigned to the global variable ANLU, referring which the three new subscreen fields are developed. So, data retrieved from database table ANLU will be passed to this FM as I_ANLU by the standard SAP main program. The value will be taken and passed to the global variable of the function group XAIS, so that the three custom fields (referring to ANLU of XAIS) get populated.
In the custom include of the function exit module EXIT_SAPLAIST_003, the following code will be written:-
E_ANLU = ANLU. The changed values in the subscreen fields exist in global variable ANLU for the function group XAIS. This function exit module will pass the data back to the SAP main program as E_ANLU.
Proper linkage/configuration has to be done so that the new subscreens get linked to the appropriate subscreen area of the Asset master screen. This has to be done otherwise, the new custom subscreen will not be displayed in the Asset master screens.
Development
Creating a Project to include the enhancement
Go to transaction CMOD and create a project.
Enter a description for the project. Then, click on the pushbutton Enhancement Assignments in the Application Toolbar.
Enter the name of the enhancement and Save.
Go to Components.
Creating Custom Include for ANLU
The screen shown below will appear, showing all the enhancement components under the assignment AIST0002. Double-click on the name of the Include Structure to create it.
Create the include structure with three new fields, as required. Then, save and activate it.
Develop the subscreen and the program
Go to transaction SE80. For the function group XAIS, create a new subscreen 9000.
Create it as subscreen.
Then, go to the Layout of the screen and create three new fields from Database table ANLU.
Drag the fields in the screen body and place them.
Then, save and activate the screen and come back to screen flow editor.
Create the PAI module to add validation for field Location 2, as required .
Activate the whole function group and come out.
Write code in the Function Exits to synchronize the programs
Now, code has to be written in the function modules EXIT_SAPLAIST_002 and EXIT_SAPLAIST_003 so that data flows to and fro between the main SAP program and custom subscreen program. For that, go back to transaction CMOD and change the function exits.
Write code in the function module EXIT_SAPLAIST_002 called once at the beginning of the transaction:
Write code in EXIT_SAPLAIST_003 to pass the data from the subscreen to SAP main program.
Then, activate everything the whole project and come out.
Complete the configuration to link the subscreen
The development portion is complete. Now, linking of the subscreen has to be done with the subscreen area of the main program. In most of the cases, this linking can be done in the enhancement itself. But, here, requirement is a bit different. It is done by configuration using SPRO.
Assets are created under Asset class. And for each asset class, there is a layout assigned to it. For a layout, there are multiple tab pages assigned to it. And, for each tab page, there are multiple screen groups/field groups assigned.
Here, the requirement is to create these three custom fields in the tab page General of asset master screen ( AS01/AS02/AS03/AS91).
Determine the Layout
To achieve this, first of all, we need to find out which layout is assigned to asset class 1000.For that, go to transaction AOLK( information has to be obtained from functional consultant).Select the Asset Class 1000 and click on folder General Assignment of Layout.
Here, for Asset class 1000, for all the user groups, tab layout SAP is assigned. Since layout SAP cannot be changed, it has to be copied and manipulated to include our screen group. Later, the new layout has to be assigned over here.
Create new tab layout
Go to transaction AOLA. Copy the tab layout SAP to create another layout, say, YSUB.
System will copy all the settings and will inform you about that.
Select your newly created layout and double-click on the folder Tab page titles.
You want to put your custom fields in the tab page General. So, select this tab page entry and double-click on the folder "Position of Groups".
Here, all the field groups currently residing in the tab-page General are shown. Add an entry for your newly created fields.
Select the group box from the list. An entry will come with U padded with the custom subscreen prepared by you.
Then, save and come out.
Assign the new Layout to Asset Class
Now, go to tcode AOLK and assign tab layout YSUB for asset class 1000.
Save and come out.
Test the Exit
Everything is over. Now, go to transaction code AS01/02/03 or AS91 to deal with an asset of asset class 1000. You will see your new fields added to the screen. Add values to themsave. Then, enter into the tcodes again to see whether the values entered by you are being displayed or not.
Original Source: ittoolbox.com
Regards
Anji

Error "No batch input data for screen SAPMF02D 0130" MASS tcode Msg:00344

Hi,
I am trying to update the filed "Industry"(KNA1-BRSCH) with value "RNRN" in Customer master data (XD01) through Tcode MASS for 1500 customers. I am getting error "No batch input data for screen SAPMF02D 0130" Message no. 00344. I tried to upate one customer but still the same error popped up. We tried implementing SAP note 737698 but it did not work.
Any inputs please??????

Hi,
MASS (KNA1)
Select KNA1-BRSCH
execute
select customers
give your value against New values field
and click on mass change button
Rgds
Murali. N

E-Recruiting Custom Data Fields & Flexibilization

Hi,
Our development team has added custom data fields for work experience (IT5103) via include CI_P5103. We are unable to adjust the appearance of the fields via Flexibilization.
Steps we followed:
1. Developers added fields (Z_FIELD1 & Z_FIELD2) to CI_P5103
2. Created contexts EXTRNL & INTRNL
3. Configured Flexibilization for Z_FIELD1 & Z_FIELD2 in EXTRNL for SAP/HRRCF_PROFILE/WORKEXPERIENCE_DETAIL.BSP to Hidden (Item Considered for Calculating Layout)
4. Configured Flexibilization for Z_FIELD1 & Z_FIELD2 in INTRNL for SAP/HRRCF_PROFILE/WORKEXPERIENCE_DETAIL.BSP to Display Only
5. Ran RCF_GENERATE_URLS for both EXTRNL & INTRNL
6. Both fields show on External Candidate Start Page (EXTRNL) and Internal Candidate Start Page (INTRNL) and are not affected by the Flexibilization config
Any suggestions would be greatly appreciated.
Thanks in advance.
Jason
E-Recruiting 6.0 SP11
BSPs

Deepak, thanks for the input.
I understand your feedback, but I don't see anything in that documentation that excludes custom fields from the modification of display.
Define Additional Fields says:
You can define additional fields for various infotypes in a Customer Include. The additional fields are displayed automatically on the relevant page.
Modify Fields in Interfaces says:
In this IMG activity you can switch fields on and off on certain application user interfaces and flag fields as mandatory fields. You assign these field definitions to a context in which the changes to the user interfaces are visible.
Screen flexibilization is possible for the following pages:
Candidate Profile
Namespace/Application/Page Page Name...
SAP/HRRCF_PROFILE/WORKEXPERIENCE_DETAIL.BSP Work Experience
It seems logical we should be able to alter the display for a custom field that if the field is defined in the approriate include.
I guess this could be another case of logic and SAP not following the same path.
Jason

Customized R12 Standard Purchase Order report with custom data and layout

Hi all,
We need to customize the seeded Purchase Order report in R12 to add an additional section to include cost data coming from our custom table. The key is that our customized report should be launched instead of the seeded report via various PO forms (e.g. View Document menu option, PO Communications form to email, fax and print PO, etc).
I manually set up a custom Document Type Layout for the Document "Standard Purchase Order" to use my customized template so my custom layout is shown instead of the R12 layout, but according to Oracle support the report can only draw data from a set of seeded Oracle views like po_headers_xml,po_lines_xml etc.
Any suggestions how we can add our custom data to PO report in R12?
Thanks! Mike.

Hi Mike
thats a tough one, the PO generation is a bit restrictive to say the least when it comes to customizing. It sounds like you have worked out how to get your own template in there to render the PO.
On the data front, all I can think of is to customize and replace the seeded PO view with one that incorporates your extra data.
Or, get into the page customization world and write your own extract and format concurrent program/procedure and then hook it onto the buttons where you want to launch it.
You might have more luch, response wise from the EBS PO forum.
Procurement : Procurement
OAF: OA Framework
Regards
Tim

How to add a new filed of Personnel number in FB60 data entry screen

Hello SAP Gurus,
We want to have a field to populate the Personnel number in all of the posting document entries via FB60. Besides the existing fields such as the "Doc.header text", "reference", "short text", "text" and "assignment" fields etc, are there any other fields that can be used to enter the Personnel number in the document entries? Maybe there're some fields are ready but the fields have been hidden on the data entry screen currently?
Personnel number is there in the Vendor master data in CoCd data, Accounting Info.
I checked the Field status group of the Vendor Recon A/c in OBC4 and made the personnel number as Optional from suppressed mode in FSG BS41 under Additional Account Assignment.
After doing the above, I am still not able to see the personnel number filed in FB60.
Am I missing anything else due to which I am not able to get the additional filed of personnel number in FB60 screen.
Any help would be greatly appreciated.

Hello Dear
Look FB60 screen has two parts :
The one in which you enter information related to vendor is Header Level, in this case you already assign Personnel No. in Vendor Master so no field is required as Personnel no. will be picked up from Vendor Master level.
The Other is line item level is bottom half part, if you want to assign personnel no. at Expense G/L level then if you scroll right you will find a field for Personnel no. If you can't see the field check your setting at OBVV for the field status group you assign to particular Expense G/L.
Hope you Understood
Cheers
IMK

No batch input data for screen SAPMSSY3 0131 in Sales order IDOC

I am processing Sales order IDOCS in status 64 using RBDAPP01 .Some of them error out to status 51 with the message -
No batch input data for screen SAPMSSY3 0131 .
I know the standard IDOC inbound process tries to simulate the posting in a BDC like process.
Now, I went to we19 and the screen hangs up in a pop up in the partners tab with partner type 'WE' and my shipto (which is actually filled in the IDOC), missing..upon repeatedly hitting enter, it goes thru and an idoc is posted in status 53. But still unable to get through the root of this issue.
Any, insight will help.

Hi,
I think the pop-up is generated through and user-exit for which recording is missing. This is why your idoc stays in status 64...
Handle the screen recording in the user exit IDOC_INPUT_ORDERS
user exit routine
PERFORM customer_function_dynpro.
FORM CUSTOMER_FUNCTION_DYNPRO.
CALL CUSTOMER-FUNCTION '002'
    EXPORTING DXVBAK   = XVBAK
              DVTCOMAG = VTCOMAG
              DLAST_DYNPRO = LAST_DYNPRO
              DXMESCOD = IDOC_CONTRL-MESCOD
    TABLES    DXBDCDATA = BDCDATA
              DXVBAP    = XVBAP
              DXVBEP    = XVBEP
              DYVBEP    = YVBEP
              DXVBADR   = XVBADR
              DYVBADR   = YVBADR
              DXVBPA    = XVBPA
              DXVBUV    = XVBUV
              DIDOC_DATA = IDOC_DATA
              DXKOMV    = XKOMV
              DXVEKP    = XVEKP
              DYVEKP    = YVEKP
    EXCEPTIONS
              USER_ERROR = 01.
Regards,
Krishnakumar

Custom data type causing trouble in deploying shared variable to RT target

I seem to be having some difficulty in using a network published shared variable created from a custom data type when deployed as an executable on an RT cRIO target. I'll start by describing why I believe this is where the problem lies. I created my RT VI in the LabVIEW development environment (LV 2012) and everything works fine. This VI is pretty simple because it rapidly devolved in to a debug exercise. The RT VI starts by simply blinking the User LED a couple of times and then starts a simple acquisition loop to read a few values off the hardware using the scan engine (while still blinking the User LED). After reading the hardware, the values are bundled in to a cluster and written to a network-published shared variable defined by a type def custom control. The custom control contains five dbl precision floats. If it matters, the cRIO RT system hosts the shared variable in this case.
So, I deploy this under the development environment and everything works fine. The LED blinks merrily along, telling me that the program is running properly. Running a host VI that reads the network-published shared variable yields the desired result. All is good.
Now I want the cRIO system to run this simple program autonomously at startup. I build it, set it as the startup VI, deploy it and then restart the cRIO target. The LED never starts blinking... the VI does not seem to run. I will spare you most of the debugging work and jump to the end. I basically "Diagram Disabled" various sections of code until the VI started running correctly as an executable. I kept reducing the size of the disabled code until only one thing was disabled: the write to the custom data type shared variable.
So, I guess my question is this: Are custom data types defined by type def'd custom controls allowed in executable RT programs? I've read through the cRIO Developers Guide, my NI Real Time Development course book and the Using Shared Variables white paper and I didn't see anything that forbade it. I know that there are some things not allowed in executables that are allowed in the development environment (front panel property nodes, dialog VIs, OS-specific calls, etc), but no mention of custom data type shared variables. Any ideas as to why my VI runs in the development environment but fails when compiled unless I remove the write to the network published shared variable?
Thanks in advance for your help!!
Solved!
Go to Solution.

Paolo,
So I thought that you meant to disconnect them in the build specification. Under the Additional Exclusions in the build specification, there is a check box for Disconnect Type Defs. I checked that box, recompiled, redeployed and it did not work. At this point I had to give and move forward, so I was going to convert the data typed from a cluster to an array. When I went in to change the data type in the shared variable pop-up from the project explorer, there was a big button under the variable definition that "Disconnect from Type Def". Clicked that button, recompiled, redeployed, restarted and everything worked great. Thank You!!
I suspect that I'll have to be careful if I change the definition of that data type (add an element, etc) since it is no longer connected to the data type. We'll cross that bridge when we need to.
Thanks again

XD01 Customer data Additional Screen

Similar Messages

Maybe you are looking for