Validating sub type field

Hi Experts,
Iam new to HR Abap programming environment. My requirement is : In 15 infotype, there is a LTA sub type ( leave travel allowance ). whenever user enters that LTA amount, it must be validated with Exemption Amount ( which exists in Infotype 582 in subtype LTA ). also, LTA amount should not exceed more than exemption amount.
Please give me some suggestions of how to approach in this regard.
Your suggestions are appreciated.
thanking you in advance
regards
Murali Krishna T

Hi ,
We can achieve this by using Dynamic actions. When you save the data , this dynamic action will be triggered. In that you can configured a form .In that form you can write a code to validate LTA amount.
Dynamic actions can be configured in the table T588Z.GO to maintenance view of T588Z and in that maintain entry for Info type 0015 and give a form name and Program name in which that form is written. Then write a program and write a form in that. Program type can be subroutine pool. In that form you write a code for your requirement. You can find more document on dynamic actions in SDN.
Hope this information will help you.
Thanks and Regards,
Narendra.Somarouthu

Similar Messages

How to create the sub type field in hr abap infotype

hi ,
how to create the sub type field in hr abap infotype.
regards,
venkat.

Try like this also
creating of infotype please follow these steps ...
Step 1: Create Infotypes
i. Goto Transaction PM01 To create Infotypes:
ii. Enter the Infotype Number and say create all.
iii. The following message would display:
i. PSnnnn Does not exist. How do you want to proceed?
iv. Click
v. A maintain Structure screen appears.
Fill in the short text description and the PS structure of the Infotype.
Since the fields Personnel No, Employee Begin Date, End Date, Sequential Number,Date of Last Change, Name of user who changed the object are available in the PAKEY and PSHD1 structure, define the PSnnnn structure with only the fields you required.
vi. Once the PS Structure is created, save and activate the structure.
vii. In the initial screen of PM01, now click on .
Create a new entry for the infotype.
Fill in the values as mentioned below and save.
Infotype Characteristics:
Infotype Name of the infotype_ Short Text: __Short Description________
*General Attributes :
Time constraint = 1
Check Subtype Obligatory
Display and Selection:
Select w/ start = 3 Valid record for entered data
Select w/ end = 5 Records with valid dates within the period entered
Select w/o date = 6 Read all records
Screen header = 02 Header ID
Create w/o end = 1 Default value is 31.12.9999
Technical Data:
Single screen = 2000
List screen = 3000; List Entry Checked.
viii. In the initial screen of PM01, now click on .
Choose the infotype entry in the list.
Fill in the values as mentioned below and save.
Technical Attributes:
In tab section,
The following attribute values are given:
Applicant DB Tab = PAnnnn Infotype Name
Subtype field = SUBTY
Subtype table = T591A
Subty.text tab. = T591S
Time cnstr.tab. = T591A
Prim. /Sec. = I Infotype
Period/key date = I Interval
and .
ix. Infotype Screen Modification:
Edit Screen 2000 from PM01 for the Infotype.
ABAP Editor for the Infotype Program MPnnnn00 will be displayed.
Click . Flow Logic will be displayed. There string coding of your own logic.
Regards
Pavan

How to Add Values in INVOICE SUB-TYPE field at the Invoice Header Forms

Hello,
Does any body knows how could I add/modify values in the INVOICE SUB-TYPE field at the Invoice Header Forms?. This values are related to the Globalization, in this case for the Chilean Localizations.
Thanks,
Alejandro R.

It gives any error or just does nothing?
Have you tried making another simple form with just one block and one or two items?
You can do this type of testing in these conditions.
Which version of forms are you using?

Can a field validation point to fields of another record type?

Field Validation based on another Record Type Field
I am trying to build validation into a custom object that sums fields under the Account record type.
The names of the fields from OBI (the table location and field name):
"- Account Custom Metrics".S_INT_13+"- Account Custom Metrics".S_INT_14+"- Account Custom Metrics".S_INT_11
My questions: can a field validation point to fields of another record type? My thought was that if OBI can look across record types than all of CRM should be able to, including field validations.
Thank you,
David

Hi !
I'm afraid this is not possible for the moment. You'll have to wait for the Release 16 I think to have such possibilities.
The R16 will allow you to create workflow rules accross different record types (e.g. Create a task on the Account linked to the service request when a new service request is created). I hope there will be the same possibilities with the validation rules...
Hope this will help, feel free to ask more.
Max

Error in ESS Mandatory field for Address(0006) Sub type 1

Hi Experts ,
       I configured certain fields as mandatory fields in the tables V_T588MFPROPC & V_T588MFPROPS for Address(0006) sub type 1. It is working fine in my development system and quality system . The same configuration is moved to production , it showing the error "fill all required fields" . Aprat from th V_T588MFPROPC & V_T588MFPROPS any other table to configure for mandatory filed.
with regards
Renjith

Hi Renjith ,
Kindly check the below,
1. check the badi implementation of HRXSS_PER_BEGDA
2. Check whether the note 1044777 is implemented in system
     1044777 -   Inconsistency in date handling of ESS PersInfo
3. Also this may be because of back end data also, try to create a new set of data with all the required fields and try to   edit     the same in portal because most of this issue may occur because of data.
Regards,
Meera

Process_order api - Validation Failed for Field Bill To

I am relatively new to the EBS world and I'm having some issues with calling the OE_Order_Pub.Process_order API. When I call this API I am getting a return error of "Validation failed for field - Bill To".
For a background...I have an APEX application where users can choose parts from a small part master list to add to an existing order. The existing order will not have a status of Closed or Cancelled and there will be atleast 1 line in the order before the new parts are added. The parts will be added as new lines to the order with some of the new line data defaulting to the same information as the first line. I am using EBS version 12.1.3 with a multi-org setup. It seems that the orders under one org (id=3) are working fine, but another org(id=569) they never work and keep getting the error. I am setting the context to the org of the order and initializing the apps user information with the responsibility "Order Management Super User".
Do you have any idea what could be wrong or how I can debug the error to get a little more detail?
Here is the procedure I have.
PROCEDURE TEK_ORD_PROCESS_ORDER(p_order_id IN NUMBER, p_return_code OUT NOCOPY VARCHAR2, p_status OUT NOCOPY VARCHAR2) IS
 CURSOR c_order_parts IS
 SELECT *
 FROM TEK_APEX.TEK_ORD_ORDER_PARTS
 WHERE ORDER_ID = p_order_id;
 TYPE t_parts IS TABLE OF TEK_APEX.TEK_ORD_ORDER_PARTS%ROWTYPE;
 v_order_parts t_parts;
 --Setup variables
 H_Op_Code VARCHAR2(25) DEFAULT OE_GLOBALS.G_OPR_UPDATE;
 L_Op_Code VARCHAR2(25) DEFAULT OE_GLOBALS.G_OPR_CREATE;
 v_install_type VARCHAR2(25) := 'PTO';
 v_source_id NUMBER;
 v_user_id NUMBER;
 v_resp_id NUMBER;
 v_app_id NUMBER;
 v_debug VARCHAR2(32767);
 v_oracle_order OE_ORDER_HEADERS_ALL%ROWTYPE;
 v_apex_order TEK_APEX.TEK_ORD_SALES_ORDERS%ROWTYPE;
 p_header_rec OE_Order_Pub.Header_Rec_Type;
 p_header_val_rec OE_Order_Pub.Header_Val_Rec_Type;
 p_Header_Adj_tab OE_Order_Pub.Header_Adj_Tbl_Type;
 p_Header_Adj_val_tab OE_Order_Pub.Header_Adj_Val_Tbl_Type;
 p_Header_price_Att_tab OE_Order_Pub.Header_Price_Att_Tbl_Type;
 p_Header_Adj_Att_tab OE_Order_Pub.Header_Adj_Att_Tbl_Type;
 p_Header_Adj_Assoc_tab OE_Order_Pub.Header_Adj_Assoc_Tbl_Type;
 p_Header_Scredit_tab OE_Order_Pub.Header_Scredit_Tbl_Type;
 p_Header_Scredit_val_tab OE_Order_Pub.Header_Scredit_Val_Tbl_Type;
 p_line_tab OE_Order_Pub.Line_Tbl_Type;
 p_line_val_tab OE_Order_Pub.Line_Val_Tbl_Type;
 p_Line_Adj_tab OE_Order_Pub.Line_Adj_Tbl_Type;
 p_Line_Adj_val_tab OE_Order_Pub.Line_Adj_Val_Tbl_Type;
 p_Line_price_Att_tab OE_Order_Pub.Line_Price_Att_Tbl_Type;
 p_Line_Adj_Att_tab OE_Order_Pub.Line_Adj_Att_Tbl_Type;
 p_Line_Adj_Assoc_tab OE_Order_Pub.Line_Adj_Assoc_Tbl_Type;
 p_Line_Scredit_tab OE_Order_Pub.Line_Scredit_Tbl_Type;
 p_Line_Scredit_val_tab OE_Order_Pub.Line_Scredit_Val_Tbl_Type;
 p_Lot_Serial_tab OE_Order_Pub.Lot_Serial_Tbl_Type;
 p_Lot_Serial_val_tab OE_Order_Pub.Lot_Serial_Val_Tbl_Type;
 p_action_request_tab OE_Order_pub.Request_Tbl_Type;
 l_header_rec OE_Order_Pub.Header_Rec_Type;
 l_header_val_rec OE_Order_Pub.Header_Val_Rec_Type;
 l_Header_Adj_tab OE_Order_Pub.Header_Adj_Tbl_Type;
 l_Header_Adj_val_tab OE_Order_Pub.Header_Adj_Val_Tbl_Type;
 l_Header_price_Att_tab OE_Order_Pub.Header_Price_Att_Tbl_Type;
 l_Header_Adj_Att_tab OE_Order_Pub.Header_Adj_Att_Tbl_Type;
 l_Header_Adj_Assoc_tab OE_Order_Pub.Header_Adj_Assoc_Tbl_Type;
 l_Header_Scredit_tab OE_Order_Pub.Header_Scredit_Tbl_Type;
 l_Header_Scredit_val_tab OE_Order_Pub.Header_Scredit_Val_Tbl_Type;
 l_line_tab OE_Order_Pub.Line_Tbl_Type;
 l_line_val_tab OE_Order_Pub.Line_Val_Tbl_Type;
 l_Line_Adj_tab OE_Order_Pub.Line_Adj_Tbl_Type;
 l_Line_Adj_val_tab OE_Order_Pub.Line_Adj_Val_Tbl_Type;
 l_Line_price_Att_tab OE_Order_Pub.Line_Price_Att_Tbl_Type;
 l_Line_Adj_Att_tab OE_Order_Pub.Line_Adj_Att_Tbl_Type;
 l_Line_Adj_Assoc_tab OE_Order_Pub.Line_Adj_Assoc_Tbl_Type;
 l_Line_Scredit_tab OE_Order_Pub.Line_Scredit_Tbl_Type;
 l_Line_Scredit_val_tab OE_Order_Pub.Line_Scredit_Val_Tbl_Type;
 l_Lot_Serial_tab OE_Order_Pub.Lot_Serial_Tbl_Type;
 l_Lot_Serial_val_tab OE_Order_Pub.Lot_Serial_Val_Tbl_Type;
 l_ret_status VARCHAR2(200);
 l_msg_count NUMBER;
 l_msg_data VARCHAR2(200);
 --Email information
 v_email_address varchar2(100);
 v_msg_text varchar(1000);
 v_subject_text varchar(1000);
 --Default line information
 v_item_id NUMBER;
 v_contact_id NUMBER;
 v_invoice_to_org_id oe_order_lines_all.INVOICE_TO_ORG_ID%TYPE;
 v_ship_to_org_id oe_order_lines_all.SHIP_TO_ORG_ID%TYPE;
 v_sold_to_org_id oe_order_lines_all.SOLD_TO_ORG_ID%TYPE;
 v_flow_status_code oe_order_lines_all.FLOW_STATUS_CODE%TYPE;
 FUNCTION GET_ORACLE_ORDER(p_order_number IN OE_ORDER_HEADERS_ALL.ORDER_NUMBER%TYPE)
 RETURN OE_ORDER_HEADERS_ALL%ROWTYPE IS
 v_order OE_ORDER_HEADERS_ALL%ROWTYPE;
 BEGIN
 SELECT *
 INTO v_order
 FROM APPS.OE_ORDER_HEADERS_ALL
 WHERE ORDER_NUMBER = p_order_number;
 RETURN v_order;
 EXCEPTION
 WHEN OTHERS THEN
 RETURN NULL;
 END GET_ORACLE_ORDER;
 FUNCTION GET_APEX_ORDER(p_order_id IN TEK_APEX.TEK_ORD_SALES_ORDERS.ORDER_ID%TYPE)
 RETURN TEK_APEX.TEK_ORD_SALES_ORDERS%ROWTYPE IS
 v_order TEK_APEX.TEK_ORD_SALES_ORDERS%ROWTYPE;
 BEGIN
 SELECT *
 INTO v_order
 FROM TEK_APEX.TEK_ORD_SALES_ORDERS
 WHERE ORDER_ID = p_order_id;
 RETURN v_order;
 EXCEPTION
 WHEN OTHERS THEN
 RETURN NULL;
 END GET_APEX_ORDER;
 FUNCTION GET_SOURCE_ID(p_source_name IN VARCHAR2)
 RETURN OE_ORDER_SOURCES.ORDER_SOURCE_ID%TYPE IS
 v_source_id OE_ORDER_SOURCES.ORDER_SOURCE_ID%TYPE;
 BEGIN
 SELECT ORDER_SOURCE_ID
 INTO v_source_id
 FROM APPS.OE_ORDER_SOURCES
 WHERE NAME = p_source_name;
 RETURN v_source_id;
 EXCEPTION
 WHEN OTHERS THEN
 RETURN NULL;
 END GET_SOURCE_ID;
 FUNCTION GET_ITEM_ID(p_part_number IN VARCHAR2, p_org_id IN NUMBER)
 RETURN MTL_SYSTEM_ITEMS.INVENTORY_ITEM_ID%TYPE IS
 v_item_id MTL_SYSTEM_ITEMS.INVENTORY_ITEM_ID%TYPE;
 BEGIN
 SELECT INVENTORY_ITEM_ID
 INTO v_item_id
 FROM APPS.MTL_SYSTEM_ITEMS
 WHERE SEGMENT1 = p_part_number
 AND ORGANIZATION_ID = p_org_id;
 RETURN v_item_id;
 EXCEPTION
 WHEN OTHERS THEN
 RETURN NULL;
 END GET_ITEM_ID;
BEGIN
 apps.mo_global.set_policy_context('S',3);
 apps.mo_global.init('XXTEK');
 BEGIN
 SELECT USER_ID
 INTO v_user_id
 FROM APPS.FND_USER
 WHERE USER_NAME = 'SYSADMIN';
 EXCEPTION
 WHEN OTHERS THEN
 RAISE_APPLICATION_ERROR(-20001, 'Error selecting user');
 END;
 BEGIN
 SELECT RESPONSIBILITY_ID, APPLICATION_ID
 INTO v_resp_id, v_app_id
 FROM TEK_APEX.TEK_RR_ACTIVE_RESP_VW
 WHERE UPPER(RESPONSIBILITY_NAME) = 'ORDER MANAGEMENT SUPER USER';
 --Set current user information
 fnd_global.apps_initialize (user_id => v_user_id
 ,resp_id => v_resp_id
 ,resp_appl_id => v_app_id);
 EXCEPTION
 WHEN OTHERS THEN
 RAISE_APPLICATION_ERROR(-20001, 'Error selecting responsibility');
 END;
 --Get the order information from Oracle and APEX
 v_apex_order := GET_APEX_ORDER(p_order_id);
 IF v_apex_order.ORDER_ID IS NULL THEN
 RAISE_APPLICATION_ERROR(-20001, 'APEX Order ID is invalid: ' || p_order_id);
 END IF;
 v_oracle_order := GET_ORACLE_ORDER(TO_NUMBER(v_apex_order.ORDER_NUMBER));
 IF v_oracle_order.ORDER_NUMBER IS NULL THEN
 RAISE_APPLICATION_ERROR(-20001, 'Order Number not found in Oracle: ' || v_apex_order.ORDER_NUMBER);
 END IF;
 apps.mo_global.set_policy_context('S', v_oracle_order.ORG_ID);
 v_source_id := GET_SOURCE_ID('IMPORT');
 IF v_source_id IS NULL THEN
 RAISE_APPLICATION_ERROR(-20001, 'Source ID not found for IMPORT');
 END IF;
 /* ********** Gather Order Header********** */
 /* ********** Info. ********** */
 OE_Order_Pub.Get_Order(p_api_version_number => 1.0,
 p_init_msg_list => FND_API.G_TRUE,
 p_return_values => FND_API.G_TRUE,
 x_return_status => l_ret_status,
 x_msg_count => l_msg_count,
 x_msg_data => l_msg_data,
 p_header_id => v_oracle_order.HEADER_ID,
 p_header => NULL,
 x_header_rec => l_header_rec,
 x_header_val_rec => l_header_val_rec,
 x_Header_Adj_tbl => l_Header_Adj_tab,
 x_Header_Adj_val_tbl => l_Header_Adj_val_tab,
 x_Header_price_Att_tbl => l_Header_price_Att_tab,
 x_Header_Adj_Att_tbl => l_Header_Adj_Att_tab,
 x_Header_Adj_Assoc_tbl => l_Header_Adj_Assoc_tab,
 x_Header_Scredit_tbl => l_Header_Scredit_tab,
 x_Header_Scredit_val_tbl=> l_Header_Scredit_val_tab,
 x_line_tbl => l_line_tab,
 x_line_val_tbl => l_line_val_tab,
 x_Line_Adj_tbl => l_Line_Adj_tab,
 x_Line_Adj_val_tbl => l_Line_Adj_val_tab,
 x_Line_price_Att_tbl => l_Line_price_Att_tab,
 x_Line_Adj_Att_tbl => l_Line_Adj_Att_tab,
 x_Line_Adj_Assoc_tbl => l_Line_Adj_Assoc_tab,
 x_Line_Scredit_tbl => l_Line_Scredit_tab,
 x_Line_Scredit_val_tbl => l_Line_Scredit_val_tab,
 x_Lot_Serial_tbl => l_Lot_Serial_tab,
 x_Lot_Serial_val_tbl => l_Lot_Serial_val_tab);
 --Save defaults from first line
 IF l_line_tab.EXISTS(1) THEN
 v_contact_id := l_line_tab(1).SHIP_TO_CONTACT_ID;
 v_invoice_to_org_id := l_line_tab(1).INVOICE_TO_ORG_ID;
 v_ship_to_org_id := l_line_tab(1).SHIP_TO_ORG_ID;
 v_sold_to_org_id := l_line_tab(1).SOLD_TO_ORG_ID;
 v_flow_status_code := l_line_tab(1).FLOW_STATUS_CODE;
 END IF;
 --Clear out the line array before adding any new parts
 FOR i IN l_line_tab.FIRST..l_line_tab.LAST LOOP
 l_line_tab.DELETE(i);
 l_line_val_tab.DELETE(i);
 l_line_adj_tab.DELETE(i);
 l_line_adj_val_tab.DELETE(i);
 l_line_price_att_tab.DELETE(i);
 l_line_adj_att_tab.DELETE(i);
 l_line_adj_assoc_tab.DELETE(i);
 l_line_scredit_tab.DELETE(i);
 l_line_scredit_val_tab.DELETE(i);
 l_lot_serial_tab.DELETE(i);
 l_lot_serial_val_tab.DELETE(i);
 END LOOP;
 /* ********** Gather Order Lines ********** */
 OPEN c_order_parts;
 FETCH c_order_parts BULK COLLECT INTO v_order_parts;
 CLOSE c_order_parts;
 FOR i IN v_order_parts.FIRST..v_order_parts.LAST LOOP
 v_item_id := GET_ITEM_ID(v_order_parts(i).PART_NUMBER, v_oracle_order.SHIP_FROM_ORG_ID);
 IF v_item_id IS NULL THEN
 RAISE_APPLICATION_ERROR(-20001, 'Error selecting part number ' || v_order_parts(i).PART_NUMBER);
 END IF;
 --Clear line first
 l_line_tab(i) := OE_Order_Pub.G_Miss_Line_Rec;
 l_line_val_tab(i) := OE_ORDER_PUB.G_MISS_LINE_VAL_REC;
 l_line_adj_tab(i) := OE_ORDER_PUB.G_MISS_LINE_ADJ_REC;
 l_line_adj_val_tab(i) := OE_ORDER_PUB.G_MISS_LINE_ADJ_VAL_REC;
 l_line_price_att_tab(i) := OE_ORDER_PUB.G_MISS_LINE_PRICE_ATT_REC ;
 l_line_adj_att_tab(i) := OE_ORDER_PUB.G_MISS_LINE_ADJ_ATT_REC;
 l_line_adj_assoc_tab(i) := OE_ORDER_PUB.G_MISS_LINE_ADJ_ASSOC_REC;
 l_line_scredit_tab(i) := OE_ORDER_PUB.G_MISS_LINE_SCREDIT_REC;
 l_line_scredit_val_tab(i) := OE_ORDER_PUB.G_MISS_LINE_SCREDIT_VAL_REC;
 l_lot_serial_tab(i) := OE_ORDER_PUB.G_MISS_LOT_SERIAL_REC;
 l_lot_serial_val_tab(i) := OE_ORDER_PUB.G_MISS_LOT_SERIAL_VAL_REC;
 --Set line information
 l_line_tab(i).PRICE_LIST_ID := v_oracle_order.PRICE_LIST_ID;
 l_line_tab(i).header_id := v_oracle_order.header_id;
 l_line_tab(i).inventory_item_id := v_item_id;
 l_line_tab(i).ordered_quantity := v_order_parts(i).QUANTITY;
 l_line_tab(i).operation := l_op_code;
 l_line_tab(i).unit_list_price := 0;
 l_line_tab(i).ship_from_org_id := v_oracle_order.ship_from_org_id;
 l_line_tab(i).program_id := fnd_global.conc_program_id ;
 l_line_tab(i).program_application_id := fnd_global.PROG_APPL_ID;
 l_line_tab(i).order_source_id := v_source_id;
 l_line_tab(i).calculate_price_flag := 'N' ;
 l_line_tab(i).unit_selling_price := 0.00 ;
 l_line_tab(i).request_date := v_apex_order.onsite_date;
 l_line_tab(i).Schedule_ship_date := v_apex_order.onsite_date;
 l_line_tab(i).promise_date := null;
 l_line_tab(i).invoice_to_org_id := v_invoice_to_org_id;
 l_line_tab(i).ship_to_org_id := v_ship_to_org_id;
 l_line_tab(i).sold_to_org_id := v_sold_to_org_id;
 l_line_tab(i).ship_to_contact_id := v_contact_id;
 END LOOP;
--OE_DEBUG_PUB.DEBUG_ON;
--OE_DEBUG_PUB.Initialize;
--OE_DEBUG_PUB.SetDebugLevel(5);
 --Add lines to order
 OE_Order_Pub.Process_order(p_api_version_number => 1.0,
 p_init_msg_list => FND_API.G_TRUE,
 p_return_values => FND_API.G_TRUE,
 p_action_commit => FND_API.G_FALSE,
 x_return_status => l_ret_status,
 x_msg_count => l_msg_count,
 x_msg_data => l_msg_data,
 p_header_rec => l_header_rec,
 p_old_header_rec => l_header_rec,
 p_header_val_rec => l_header_val_rec,
 p_old_header_val_rec => l_header_val_rec,
 p_Header_Adj_tbl => l_Header_Adj_tab,
 p_old_Header_Adj_tbl => l_Header_Adj_tab,
 p_Header_Adj_val_tbl => l_Header_Adj_val_tab,
 p_old_Header_Adj_val_tbl => l_Header_Adj_val_tab,
 p_Header_price_Att_tbl => l_Header_price_Att_tab,
 p_old_Header_Price_Att_tbl => l_Header_price_Att_tab,
 p_Header_Adj_Att_tbl => l_Header_Adj_Att_tab,
 p_old_Header_Adj_Att_tbl => l_Header_Adj_Att_tab,
 p_Header_Adj_Assoc_tbl => l_Header_Adj_Assoc_tab,
 p_old_Header_Adj_Assoc_tbl => l_Header_Adj_Assoc_tab,
 p_Header_Scredit_tbl => l_Header_Scredit_tab,
 p_old_Header_Scredit_tbl => l_Header_Scredit_tab,
 p_Header_Scredit_val_tbl => l_Header_Scredit_val_tab,
 p_old_Header_Scredit_val_tbl => l_Header_Scredit_val_tab,
 p_line_tbl => l_line_tab,
 p_line_val_tbl => l_line_val_tab,
 p_Line_Adj_tbl => l_line_adj_tab,
 p_Line_Adj_val_tbl => l_line_adj_val_tab,
 p_Line_price_Att_tbl => l_line_price_att_tab,
 p_Line_Adj_Att_tbl => l_line_adj_att_tab,
 p_Line_Adj_Assoc_tbl => l_line_adj_assoc_tab,
 p_Line_Scredit_tbl => l_line_scredit_tab,
 p_Line_Scredit_val_tbl => l_line_scredit_val_tab,
 p_Lot_Serial_tbl => l_lot_serial_tab,
 p_Lot_Serial_val_tbl => l_lot_serial_val_tab,
 p_action_request_tbl => OE_ORDER_PUB.G_MISS_REQUEST_TBL,
 x_header_rec => p_header_rec,
 x_header_val_rec => p_header_val_rec,
 x_Header_Adj_tbl => p_Header_Adj_tab,
 x_Header_Adj_val_tbl => p_Header_Adj_val_tab,
 x_Header_price_Att_tbl => p_Header_price_Att_tab,
 x_Header_Adj_Att_tbl => p_Header_Adj_Att_tab,
 x_Header_Adj_Assoc_tbl => p_Header_Adj_Assoc_tab,
 x_Header_Scredit_tbl => p_Header_Scredit_tab,
 x_Header_Scredit_val_tbl => p_Header_Scredit_val_tab,
 x_line_tbl => p_line_tab,
 x_line_val_tbl => p_line_val_tab,
 x_line_adj_tbl => p_line_adj_tab,
 x_line_adj_val_tbl => p_line_adj_val_tab,
 x_line_price_att_tbl => p_line_price_att_tab,
 x_line_adj_att_tbl => p_line_adj_att_tab,
 x_line_adj_assoc_tbl => p_line_adj_assoc_tab,
 x_line_scredit_tbl => p_line_scredit_tab,
 x_line_scredit_val_tbl => p_line_scredit_val_tab,
 x_lot_serial_tbl => p_lot_serial_tab,
 x_lot_serial_val_tbl => p_lot_serial_val_tab,
 x_action_request_tbl => p_action_request_tab);
-- OE_DEBUG_PUB.DEBUG_OFF;
 p_return_code := l_ret_status;
 IF l_ret_status != 'S' THEN
 DBMS_OUTPUT.PUT_LINE(l_msg_data);
 IF l_msg_count = 1 THEN
 p_status := OE_Msg_Pub.Get(1,'F');
 ELSE
 FOR i IN 1..l_msg_count LOOP
 p_status := OE_Msg_Pub.Get(i,'F') || ' ';
 END LOOP;
 END IF;
 p_status := 'Error loading lines ' || p_status;
 ELSE
 p_status := 'Order Processed Successfully ' || v_order_parts.COUNT || ' Line(s) Loaded';
 END IF;
-- WHILE OE_DEBUG_PUB.G_DEBUG_INDEX < OE_DEBUG_PUB.CountDebug LOOP
-- OE_DEBUG_PUB.GetNext(v_debug);
-- DBMS_OUTPUT.PUT_LINE(v_debug);
-- END LOOP;
EXCEPTION
 WHEN OTHERS THEN
 ROLLBACK;
 RAISE;
END TEK_ORD_PROCESS_ORDER;Thanks!
Jonathan Hart

Hello,
Try the following
1) Check if any processing constraints are applied to customer/location
2) Try to create a new customer and associate internal location.
Create a new order to reproduce the issue
Thanks
-Arif

Handling pop up of sub type HR_MAINTAIN_MASTERDATA

Hi All,
I am using HR_MAINTAIN_MASTERDATA for creating employee it's working fine but i am not able to handle pop up for sub type.
For example sub type for Address it gives me pop up with values 1 Permamant address 2 Office address.
Anybody know how to handle such pop up in function module. How to provide values to sub type.
Thanks in advance.

HI R P,
The field SUBTY is there as an export parameter for function module you mentioned.
Please pass the value for that field when you call the FM in your program.
Hope this helps
Ajay

To find the date type fields in the row and validate those date fields

TYPES : BEGIN OF TY_MARA,
          MATNR TYPE MARA-MATNR,
          ERSDA TYPE MARA-ERSDA,
          ERNAM TYPE MARA-ERNAM,
          LAEDA TYPE MARA-LAEDA,
          MTART TYPE MARA-MTART,
        END OF TY_MARA.
DATA : it_mara TYPE STANDARD TABLE OF ty_mara,
      it_mara1 TYPE STANDARD TABLE OF ty_mara,
       wa_mara TYPE ty_mara.
loop at it_mara into wa_mara.
describe field wa_mara-ersda type c_data.
if c_data eq 'D'.
CALL FUNCTION 'DATE_CHECK_PLAUSIBILITY'
    EXPORTING
      date                            = wa_mara-ersda
   EXCEPTIONS
     PLAUSIBILITY_CHECK_FAILED       = 1
     OTHERS                          = 2
IF sy-subrc eq 0.
wa_mara-ersda = '00000000'.
    append wa_mara to it_mara1.
    write :wa_mara-matnr,wa_mara-ersda.
    else.
        wa_mara-ersda = '00000000'.
    append wa_mara to it_mara1.
    write :wa_mara-matnr,wa_mara-ersda.
ENDIF.
endif.
endloop.
This issue regarding how to find the date type fields in the row and validate those date fields.If its not a valid date ,i have to assign initial value to that.
I've tried that for single field using describe field.Please help me do that for all fields.

Hi Sam,
I believe we had discussed the same issue in the below thread. Can you please refer the below one?
http://social.msdn.microsoft.com/Forums/sharepoint/en-US/d93e16ff-c123-4b36-b60b-60ccd34f6ca7/calculate-time-differences-in-infopath?forum=sharepointcustomizationprevious
If it's not helping you please let us know
Sekar - Our life is short, so help others to grow
Whenever you see a reply and if you think is helpful, click "Vote As Helpful"! And whenever
you see a reply being an answer to the question of the thread, click "Mark As Answer

Validation fo Reference Field

Dear Expet's,
i have created validation for Reference field(f-43) for one company and activated it, but its not checking it.
Prerequisite:
BKPF-BUKRS = '6560' AND BKPF-BLART = 'KR'
Check:
BKPF-XBLNR = ''
Message:
Please check reference field!
can someone help in this!

You can use the standard validation instead of the code you are programming. You activate it where you define the class type. The path under the IMG is: Financial Accounting (New) >> Financial Accounting Global Settings (New) >> Document Document Types >> Define Document Types for Entry View. Then, find the document type, double click on it and check the box Reference number. Save.
Assign points if the information was useful.

Use of construction type field in Equipment master

Dear All,
What is the use of construction type field in equipment master and how can i use in plant maintenance processes or transactions
If possible give some examples.Also any one have some document or link related to construction type, kindly provide.
Thanks & Regards,
Sandeep

Construction Type is used for identify the equipments having similar construction of materials.
For examples: Identical Mechanical seal used in different pumps.
A BOM can be linked to a technical object in two ways:
By direct assignment: directly assigned BOM
If you create a bill of material directly for a technical object, it is assigned directly. If all the technical objects are identical in terms of structure, the BOM items are valid for all the allocated technical objects.
By indirect assignment: indirectly assigned BOM
For technical objects that have a material BOM - if you enter a material number in the Construction type field of a master record, the material BOM is indirectly assigned to the object. This is a good idea when a company has several identical technical objects grouped under one material number.
Regards
Dhiren

Enhacmnet and addition of new sub types

Hi SAP gurus
1) I want to add one more subtype in the infotype 28 Internal mediacl services.The sub type will be named as Family history and and in all aspect it would be same as other sub type like 0001. In this sub type i want to add three Fields
A) Diabitic in whch only specifiv values will be entered which will yes or no
B) Hyper tension in whch only specifiv values will be entered which will yes or no
So on .............
2) And i also want to modify the existing sub types like in sub type 0001 under the field Phys.constitution i want to store some fixed values like blood group.
I also want to add one more field Veins which will also have specific values like Yes/No
How can i do this
Please help in this regard its really urgent. reward point guranted for helping solutions.

New Subtypes can be added via SM30/31 by maintaining V_T591A for 0028.
Infotype can be enhanced using TCode PM01.
Pl search the forumon how to enhance the Infotype. there are quitea few helpful threads on this issue.
~Suresh

Sub Category Field

Dear All,
I need to sub divided my categories into Sub Category. I am planning to change the Subject Field into Sub Category Field and mainatain the sub category entries via Code and Code group.
I need to know some details
a. whether this subject field in used any where else.
b. Shall i create a new field and instead of changing the Subject Field. But I have 1 constraint in creating new field as this new field wil not reflect in the standard crm_dno_monitor report.
Please suggest the best solution.
Raj

Hi,
Better create a new Sub Profile & Code Group and assign it to your Txn Type.
Also, you can use this code groups in your CRM_DNO_MONITOR report.
Thx,
Waseem.

Enter a valid basic type - BW IDoc type RSSEND is not same as the SS IDOC

Hi,
I am connecting the ERP system to BW system, and am getting error:
CHECK(context menu source system):
@5C@     BW unknown in source system     RSAR     8
@5C@     The BW IDoc type RSSEND is not the same as the source system IDoc type     RSAR     371
RESTORE(context menu source system):
Information: Enter a valid basic type
Information help:
Enter a valid basic type
    Message no. E0434
Diagnosis
    An entry with the key /BD2CLNT100/LS//RSSEND//// is to be inserted in
    table
    EDP13.
    The value 'RSBEND' is not valid for field IDOCTYP.
Procedure
    Check whether basic type RSBEND exists.
help required

Hi,
Please find the below link may useful.
http://wiki.ittoolbox.com/index.php/Re-Connect_R/3_and_BW
Reg,
Venkat

GRC CUP employee type field

Hi,
How can i restrict Employee type field "consultant" with valid from and valid to, maximum 6 months.
Thanks
Yakoob

You'd have to talk to your LDAP people, but they'd have to maintain the field for external employees, then!
Why not create a different initiator for that employee type and make sure the approver takes care of that?
Frank.

Validation on multi fields

Created a form on a table. table1 has columns:id (not null),fname,lname,div
Need a validation: if all 3 fields are empty (fname,lname, div) then don't accept the input from the form.
How do you do a validation on multiple fields in apex? I can write a function like
if (:fname is null and :lname is null and :div is null ) then return True else return False.
But how do you put this into the condition under the process section in Apex? basically it means if all 3 fields are null then don't execute the process row of table1 when user click create button.
Can someone give me some pointers? Many thanks in advance.
tai

Tai,
You can create page level validations in APEX where you can do what you have specified.
In Page definition, click on + sing against 'Validations', Slelect 'Page level validation' and click NEXT, Select 'PL/SQL' click next and here select 'function returning boolean' and put your code.
Return FALSE -- if validation fails
Cheers
Hari

Validating sub type field

Similar Messages

Maybe you are looking for