Output type not triggered during Delivery Order - pls help

Hi,
Need some help.
I'm trying to setup output determination for delivery. It's a new output type for delivery.
There are some checking that I want to build in to determine whether the output type is to be generated. Therefore I have to make sure of requirement (routine). However, after putting in the configuration, coding the requirement and creating the condition record, the output type still cannot be generated. When I go to VL02N to check the Output Determination Analysis it says the requirement " " is not fulfilled. It's not even calling out the requirement number that I assigned in the access sequence.
Any idea what could be wrong?
This is what I've done :
1. Creating condition tables
2. Creating access sequence & assigning the condition tables to the access sequence
3. In the access sequence, assign requirement number 999. The "Exclusive" indicator is not ticked.
4. Ensure that the requirement 999 is activated in tcode VOFM.
5. Create output type, assign the access sequence to the condition type.
6. Assign the condition type to the output determination procedure. Make sure the "Manual" checkbox is not ticked.
7. Assign the delivery type to the output determination procedure.
8. Create condition record.
Note : when i created the condition record, I am not able to assign a Partner Function (for eg. SH) to the record. However in the config for the output type I've already configured for that Partner Function "SH" to be allowed for that output type.
Appreciate suggestions & feedback.
Thanks
Rgds,
L

Hi,
When I go to VL02N to check the Output Determination Analysis it says the requirement " " is not fulfilled. It's not even calling out the requirement number that I assigned in the access sequence.
This is because in requirement you put certain conditions should be fulfill then out put should trigered,
Example - if you maintained condition in requirement that user must maintain loading point
Now when creating delivery user not maintained loading point then output will not trigered, so user must maintain that then only it will trigered output.
Same problem just now solved, check which data maintenance conditions in routine and try to maintain that.
Kapil

Similar Messages

Output type not triggering

Hi,
I have maintained a condition record for the output type in my billing document. It should be triggered automatically.What are settings that I should check?
NOTE:- I am using an already existing o/p type and o/p procedure.Only the differentiation factor this time is that the sales organization is different than the previous one.So, have maintained only the condition record for the new sales organization.
After maintaining the condition record, the o/p type should get trigger automatically in my billing document which doesn't happen.Kindly throw some light on it.

>
Amit Yadav wrote:
> Dear Christino,
>
> Check with Condition record in T. Code: VV31/ 32.
>
> Key-in your Sales Org and Billing Type
>
> Maintain row-entry as:
>
> Bill Type-----FunctionMedium--
Date/time
>
> once maintained, click tab: Communicaion
>
> within this, Maintain Output device and check box: Print immediately (if, medium is 1).
>
> Best Regards,
>
> Amit
Hi Christino,
Along with Amit's points pls check that in further data whether option 4(Saving the applaication) is maintained or not.
Regards,
Mohan.

Output type not triggered on time

Dear All,
I have an issue on output determination.
We have a list of outputs on Delivery which will be determined after the loading start checked in Shipment based on activity profile assigned to the Shipment type.
Out of all the outputs, only one output is not printed on time (But it is determined on time).
We checked the condition record and everything, all found ok. But still we are facing this issue.
Could anyone suggest me on this.
Regards,
Mullairaja

Hi Mullairaj,
If i understand it right, you are able to trigger output for both the cases but only one is picked by batch job and so you are only seeing one "Green" output but the other stays "Yellow". if this is right then did you check if the batch job is calling program RSNAST00 with right variants ?. Does this JOB has variant to pick both the Outputs.
Let me know.
Thanks!

Output type not determined during background Job

Hi Experts,
we have scheduled a Job to create Billing. In few of the billing documents, output type is not getting determined. Condition records are maintained correctly. This is happening only for few billing documents in spite of maintaining condition records?
Can some one help me on this issue.

shravan,
added: How do users come to know that in few documents output is not getting determined?
To check determination of output record - In VF02, give the billing document for which output was not determined.
Goto > Header > Output, check if the output has got determined.
If not then it is not getting determined.
any difference between the documents in which output is getting determined and in which not?
TW
Message was edited by: TW Typewriter

Output type not determined in Sales Order

Hello Friends,
I am facing a problem.
I have maintained the O/P condition record for O/P type for order confirmation.
While creating sales order, in the determination analysis for O/P , it shows as O/P found, but the same is not added in the sales Order outputs.
Can somebody advise me what is missing ?
Regards

Harsh Mathur ,
1. You need to maintain Condition records in VV11 for BA00 (Key combination - order type)
2. If already created Check whether the records are existing through VV12
3. If yes, then enter into your sales order in VA02 Mode
4. Check Extras --> Output --> Header --> Edit
If status is yellow or green then it is ok. Output = BA00, Medium = Print output, Function = SP
Then Choose the line and click "Communication Method" Enter Logical destination - LP01 and activate the indicator against "Print Immediately"
Click Back button --> Click "Further Data"
Under "Requested Processing" header
Dispatch time = Choose the option accordingly
save it.
Then counter check the config by running sales transaction without saving check
Check Extras --> Output --> Header --> Print Preview
if the output is shown then you have succeded
Regards
Sathya

Delivery Output Type not updated automatically in change mode

Hello,
I am dealing with a strange problem.
If i open delivery to change using VL02N then, output type configured for reissue is updated properly and on save ouput type is getting successfully processed also.
Now if i open VL03N and then using change mode button on application toolbar i go to change of delivery, then output type is not getting created. The issue was figured out when i tried to open delivery from shipment and then using change button i tried to change and save delivery....
Expectiing solution from experts.
Thanks
Hari

Hi,
May be this behaviour is due to the application in which you are opening the delivery. When you open the delivery from shipment, check the transaction code in the screen in system status. If it is VL03N, then it is correct. But if it is VT03N, then it is expected that even in change mode, the output is not triggered. Pls check this once.
I tried the same thing in an invoice from where i opened a SO and then went in change mode, and the otuput is getting retriggered.
I hope teh configuration of your output is correct. Ensure that the Multiple Issuing button is ticked on, if you want yoru output type is to be triggered everytime you go in change mode.

BBP_PO_SEND_XML - Not triggered during the creation of PO

Hi All,
We are using SRM 7.0, configuration for sending PO in the form of XML is done as suggested with the method BBP_PO_SEND_XML. The problem is, this BADI is not triggered when we save (even after order) the PO with XML option and the status is displayed as Incorrectly processed. But, when I select the Incorrectly processed output type and click on Repeat Output, the BADI is called and is processed succesfully.
Any reasons, why the BADI is not triggered during the creation or change of PO and is getting triggered only when we select the option Repeat Output? Please help me in correcting this issue.
Thanks,
Phani.

Logic inside META_PO_SEND was written in user name check. Whereas the method BBP_PO_SEND_XML is triggered with batch user. Due to this reason, custom logic is not triggered.

QM Block not triggered via EDI orders

Hello All,
Please help me with this problem "QM block not triggered via EDI Orders".
Sales Orders will be created using IDOC. When the sales orders was displayed using VA02, goto >> items >> schedule lines, there's no QM status violated being displayed in the delivery block column.
Kindly help me what logic will I applied regarding this matter.
FM used was IDOC_INPUT_ORDERS.
I need your comments/suggestions ASAP.
Thanks in advance.
Carina

hai,
Just check this it may help tou.
Program Name : YX30_UPLOAD_QUALITY_INFO
Quality Info Record for I30 System *
Original Transport Number : I30K903055 *
SYS id: SYS_30_1502_03_41_Upload Quality Info Records *
TDS id: TD_30_1502_03_41_Upload Quality Info Records *
UT ID: UT_30_1502_03_41_Upload Quality Info Records *
======================================================================
Change History *
Date | Change No | Name | Description *
yyyy/mm/dd | AAAYYYYMMDD | xxxxxxxxxxxx | *
REPORT YX30_UPLOAD_QUALITY_INFO MESSAGE-ID yx30_conversions
no standard page heading line-size 255.
include yx30_upload_quality_info_top. "Include for Variable Declaration & Selection Screen
include yx30_upload_quality_info_data. "Include for File read & Authority Check
*& At Selection Screen Output *
AT SELECTION-SCREEN OUTPUT. "PBO
PERFORM fill_parameters.
*& Start Of Selection Event *
start-of-selection.
Perform Authority_check. "Subroutine for authority check
Perform prepare_file. "Subroutine for preparing file
perform file_read. "Subroutine for File read
perform update_qi01. "Subroutine for Uploading data
perform write_error_log1. "Subroutine for writing error log
*& Form write_error_log
text
--> p1 text
<-- p2 text
*& Include YX30_UPLOAD_QUALITY_INFO_TOP
Type Declaration
Types: Begin of type_qtyinf,
matnr type matnr, "Material No
lieferant type char10, "Vendor
werk type werks_d, "Plant
frei_dat type char10, "Frei_Dat
stsma type char8, "Stsma
anwso_01 type char1, "ANWSO(01)
anwso_02 type char1, "ANWSO(02)
anwso_03 type char1, "ANWSO(03)
end of type_qtyinf.
Internal Table Declaration
Data: itab_qtyinf type standard table of type_qtyinf. "Internal table for QTYINF.
Work Area Declaration
Data: wa_qtyinf type type_qtyinf. "Work Area for QTYINF.
Variable Declaration
Data: v_file_qtyinf type string, "Source File Name
v1 type string,
v2 type string,
v3 type string,
v_file_return type string,
v_lin TYPE n.
*Selection Screen Declaration
selection-screen *
SELECTION-SCREEN BEGIN OF BLOCK blk1
WITH FRAME TITLE text-s01.
PARAMETER:
p_sysid(3) TYPE c OBLIGATORY , "Source System
p_bukrs(4) TYPE c OBLIGATORY , "Source CompCode
p_samshr type char30 lower case obligatory default '/sap_upload/' , "Samba Share Drive
p_object TYPE CHAR10 OBLIGATORY default 'MAT' . "Migration Data Object
SELECTION-SCREEN END OF BLOCK blk1.
SELECTION-SCREEN SKIP 3.
PARAMETER:
cb_pfill TYPE c AS CHECKBOX DEFAULT 'X' . "Prefill values?
SELECTION-SCREEN COMMENT /1(79) text-s1a.
SELECTION-SCREEN BEGIN OF BLOCK blk3
WITH FRAME TITLE text-s03.
PARAMETER:
pa_filn1(500) TYPE c LOWER CASE
VISIBLE LENGTH 50 , "Filename AppServer
pa_dlimt TYPE c DEFAULT ';' . "Field Delimter
SELECTION-SCREEN END OF BLOCK blk3.
include bdcrecx1. "Include for the subroutine
*& Include YX30_UPLOAD_QUALITY_INFO_DATA
*& Form file_read
Subroutine for reading the source file into internal table
--> p1 text
<-- p2 text
FORM file_read .
DATA:
single_line TYPE string .
*-- read file, split lines into fields and put data into table
OPEN DATASET v_file_qtyinf FOR INPUT IN TEXT MODE ENCODING NON-UNICODE. "Opening the files
IF sy-subrc EQ 0.
DO.
READ DATASET v_file_qtyinf INTO single_line. "Reading the content of file into line
IF sy-subrc = 0.
IF sy-index > 1. "skip header-line
SPLIT "Split the content of line into work area
single_line
AT ';'
INTO
wa_qtyinf-matnr "Material No
wa_qtyinf-lieferant "Vendor
wa_qtyinf-werk "Plant
wa_qtyinf-frei_dat "Frei Date
wa_qtyinf-stsma "STSMA
wa_qtyinf-anwso_01 "ANWSO_01
wa_qtyinf-anwso_02 "ANWSO_02
wa_qtyinf-anwso_03. "ANWSO_03
APPEND wa_qtyinf TO itab_qtyinf. "Appending Work Area to internal table
ENDIF.
ELSE.
EXIT.
ENDIF.
ENDDO.
CLOSE DATASET v_file_qtyinf. "Closing the files
ELSE.
MESSAGE e015 .
ENDIF.
DESCRIBE TABLE itab_qtyinf LINES v_lin.
IF v_lin LT 0.
MESSAGE e016 .
ENDIF.
ENDFORM. " file_read
*& Form fill_parameters
Subroutine for getting the file name
FORM fill_parameters .
IF cb_pfill = 'X'.
Preparing QTYINF File
CONCATENATE p_sysid '_forward' INTO v3.
CONCATENATE p_sysid '_QTYINF_' p_bukrs '.CSV' INTO v2.
CONCATENATE p_samshr v3 '/' p_object '/' v2 INTO pa_filn1.
ENDIF.
ENDFORM. " fill_parameters
*& Form Authority_check
Authority Check
--> p1 text
<-- p2 text
FORM authority_check .
Authority Check For the Migration
AUTHORITY-CHECK OBJECT 'YX30_MIGR'
ID 'SYSTEM' FIELD p_sysid
ID 'BUKRS' FIELD p_bukrs
ID 'YX30_DMOBJ' FIELD p_object
ID 'ACTVT' FIELD '16'.
IF sy-subrc <> 0.
MESSAGE e010 WITH p_sysid p_bukrs p_object.
ENDIF.
ENDFORM. " Authority_check
*& Form prepare_file
text
--> p1 text
<-- p2 text
FORM prepare_file .
CONCATENATE p_sysid '_forward' INTO v3.
CONCATENATE p_sysid '_QTYINF_' p_bukrs '.CSV' INTO v2.
CONCATENATE p_samshr v3 '/' p_object '/' v2 INTO v_file_qtyinf.
CLEAR v3.
CLEAR v2.
Prepare Return File
CONCATENATE p_sysid '_forward' INTO v3.
CONCATENATE p_sysid '_RETRUN_LOG_' p_bukrs '.CSV' INTO v2.
CONCATENATE '/sap_upload/' v3 '/' 'MAT' '/' v2 INTO v_file_return.
ENDFORM. " prepare_file
*& Form update_qi01
text
FORM update_qi01.
PERFORM open_group. "Opening a session
CLEAR wa_qtyinf.
LOOP AT itab_qtyinf INTO wa_qtyinf.
PERFORM bdc_dynpro USING 'SAPMQBAA' '0100'. "Subroutine for mapping data
PERFORM bdc_field USING 'BDC_CURSOR'
'QINF-MATNR'.
PERFORM bdc_field USING 'BDC_OKCODE'
'/00'.
PERFORM bdc_field USING 'QINF-MATNR'
wa_qtyinf-matnr. "Mapping the material
PERFORM bdc_field USING 'QINF-LIEFERANT'
wa_qtyinf-lieferant. "Mapping the vendor
PERFORM bdc_field USING 'QINF-WERK'
wa_qtyinf-werk. "Mapping the plant
PERFORM bdc_dynpro USING 'SAPMQBAA' '0101'.
PERFORM bdc_field USING 'BDC_OKCODE'
'=STAN'.
PERFORM bdc_field USING 'QINF-FREI_DAT'
wa_qtyinf-frei_dat.
PERFORM bdc_field USING 'BDC_CURSOR'
'QINF-STSMA'.
PERFORM bdc_field USING 'QINF-STSMA'
wa_qtyinf-stsma. "Mapping the status
PERFORM bdc_dynpro USING 'SAPLBSVA' '0201'.
PERFORM bdc_field USING 'BDC_CURSOR'
'J_STMAINT-ANWSO(01)'.
PERFORM bdc_field USING 'BDC_OKCODE'
'=OKAY'.
IF wa_qtyinf-anwso_01 = 'X'.
PERFORM bdc_field USING 'J_STMAINT-ANWSO(01)'
wa_qtyinf-anwso_01. "Mapping the anwso(01)
ELSEIF wa_qtyinf-anwso_02 = 'X'.
PERFORM bdc_field USING 'J_STMAINT-ANWSO(02)'
wa_qtyinf-anwso_02. "Mapping the anwso(02)
ELSEIF wa_qtyinf-anwso_03 = 'X'.
PERFORM bdc_field USING 'J_STMAINT-ANWSO(03)'
wa_qtyinf-anwso_03. "Mapping the anwso(03)
ELSEIF wa_qtyinf-anwso_01 = 'X' AND wa_qtyinf-anwso_02 = 'X'.
PERFORM bdc_field USING 'J_STMAINT-ANWSO(01)'
wa_qtyinf-anwso_01.
PERFORM bdc_field USING 'J_STMAINT-ANWSO(02)'
wa_qtyinf-anwso_02.
ELSEIF wa_qtyinf-anwso_01 = 'X' AND wa_qtyinf-anwso_03 = 'X'.
PERFORM bdc_field USING 'J_STMAINT-ANWSO(01)'
wa_qtyinf-anwso_01.
PERFORM bdc_field USING 'J_STMAINT-ANWSO(03)'
wa_qtyinf-anwso_03.
ELSEIF wa_qtyinf-anwso_02 = 'X' AND wa_qtyinf-anwso_03 = 'X'.
PERFORM bdc_field USING 'J_STMAINT-ANWSO(02)'
wa_qtyinf-anwso_02.
PERFORM bdc_field USING 'J_STMAINT-ANWSO(03)'
wa_qtyinf-anwso_03.
ELSEIF wa_qtyinf-anwso_01 = 'X' AND wa_qtyinf-anwso_02 = 'X' AND wa_qtyinf-anwso_03 = 'X'.
PERFORM bdc_field USING 'J_STMAINT-ANWSO(01)'
wa_qtyinf-anwso_01.
PERFORM bdc_field USING 'J_STMAINT-ANWSO(02)'
wa_qtyinf-anwso_02.
PERFORM bdc_field USING 'J_STMAINT-ANWSO(03)'
wa_qtyinf-anwso_03.
ENDIF.
PERFORM bdc_dynpro USING 'SAPMQBAA' '0101'.
PERFORM bdc_field USING 'BDC_CURSOR'
'QINF-FREI_DAT'.
PERFORM bdc_field USING 'BDC_OKCODE'
'=QMBU'.
PERFORM bdc_field USING 'QINF-FREI_DAT'
wa_qtyinf-frei_dat.
PERFORM bdc_field USING 'QINF-STSMA'
wa_qtyinf-stsma.
PERFORM bdc_transaction USING 'QI01'.
ENDLOOP.
PERFORM close_group. "Closing the session
ENDFORM. "update_qi01
*& Form write_error_log
text
--> p1 text
<-- p2 text
FORM write_error_log1 .
DATA:
single_line TYPE string,
v_msg TYPE string,
v_msg1 TYPE string.
*-- read file, split lines into fields and put data into table
OPEN DATASET v_file_return FOR INPUT IN TEXT MODE ENCODING NON-UNICODE. "Opening the files
IF sy-subrc EQ 0.
CONCATENATE text-020 v_lin INTO v_msg SEPARATED BY space.
CONCATENATE text-021 v_lin INTO v_msg1 SEPARATED BY space.
TRANSFER: v_msg TO v_file_return.
TRANSFER: v_msg1 TO v_file_return.
WRITE:/ v_msg.
WRITE:/ v_msg1.
ENDIF.
ENDFORM. " write_error_log
with regards.
sowjanya.b.

Output type mot triggered

Hi,
The process is that
A sales orders are getting created with the batch job once the sales order has been generate a Output type is triggers
and mail sents to customer about the order confirmation.
The medium os output type is "Send external" and dispatch type is "3 - Send with application own transaction"
Our problem is this output type has not getting triggered it in Yellow only.
if we change the dispatch time form 3 to 4 - Send immidetiatly then its working fine.
why this is happening?
how to resolve this so that there will be smooth operation with dispatch time as 3?
regards,
anup

See, you can process a message immediately by updating the application document or you can process it at a later time. For later processing you must use the report program RSNAST00 or a corresponding application function.
Thus there are some individual possibilities are:
Time 1: The message is processed through report program RSNAST00. This report program can be scheduled periodically or started manually.
Time 2: As in time 1, but the message contains an earliest processing date and a requested processing time. The message is ignored by report program RSNAST00 before the requested date.
Time 3: The message is selected and processed by application specific programs. Processing can take place online or in the background.
Time 4: The message is processed when the application document is saved. No further processing of the message is necessary.
So, check your communication method & transmission medium for dispatch time 3 for your requirement : A sales orders are getting created with the batch job once the sales order has been generate a Output type is triggers and mail sents to customer about the order confirmation. Check the output condition record maintained.
Also you can use user exit MV45AFZZ for automatic generation of email.
Hope this can assist you.
Thanks & Regards
JP

Credit Management not activated in Delivery Order

Hi,
I've made relevant configurations in SPRO such that during the creation of sales order, credit management is activated. A warning message popup to warn user of the credit exceeded.
However, during delivery order creation, such warning message does not get popup.
I'm using the simple credit checks. In spro->sales & distribution ->basic functions->credit management->assign sales docs & delivery docs-> credit limit check for delivery types, i've set the relevant delivery type to have credit group 02 (Delivery) & 03 (PGI). Under the item cat for delivery order, i've also checked the active credit checkbox.
Any config i've missed out?
Thanks
Regards,
HweeLing

Hi,
According to your reply, I can only set credit checks popup message at only 1 place - Either sales order OR delivery order?
Does it mean that if i have the check in sales order, I cannot have the same popup message in delivery order?
Currently, i have the popup message in sales order.
I do not want to block delivery order. I only want a warning message thats all.
Thanks

Batch split not happening during delivery

Hi Experts,
I have enough of stock for a material with different batches (with different expiry dates). When I create an order for qty 100, system confirms it on a certain date taking 1st batch nearest to expiry date, as per the search startegy set in the cponfiguration.Please note here that the batch that system picks has got only 50 qty in stock, but it shows whole 100 qty against it. Probably because Batch split is not possible during sales order creation, hence system showing whole qty against one batch.
Now, when I try to create delivery, it shows only 50 qty of the same batch in delivery document. I select the line item and go to the "Batch split" tab to effect batch split, but system does not allow. It says "Batch already specified for material".Here is the detail for your analysis-
Batch in item 000010 already specified for material 2000978
Message no. VL221
Diagnosis
The batch was either predefined in the sales order that the delivery is based on or it was assigned to the delivery item manually. Therefore, you can no longer carry out a batch split for the delivery quantity of the items.
Procedure
In order to make the batch split possible, you can cancel the assignment of the delivery item to the batch, if the delivery's processing status allows.
Kindly advise.
Thanks in advance,
Randhir

Thanks Mr. P Gomatheeswaran,
Now batch is not being determined during sales order creation, that's fine.While creating delivery,when I select line item and go to Batch split tab I can see batches being split in two, which is OK. But when I try to put Picking quantity as delivery qty, system says "Picked quantity is larger than the qty to be delivered".(Message no. VL019).
Also Storage location field is grayed out.
Regards,
Randhir

Output type not proposed in Message Control when PO is created

Hi,
DETAILS
I have set up the system to send a IDOC when a PO is created. I have done the following settings in the system to send the IDOC using the message control functionality in the PO creation screen.
1). Created a new output type ZNEU which is an exact copy of NEU output type provided by the SAP system.
2). Assigned the new output type to the output determination procedure.
3). Enabled the new output type ZNEU for ALE distribution.
4). Maintained the condition records in the system for the output type ZNEU such that for the P org, endor and Docmuent type combination the output shall be proposed.
5). Maintained a partner profile( Logical System ) and assigned the output type ZNEU to this partner profile.
6). Created a Distribution model for Sender ~ Receiver for ORDERS message type.
PROBLEM
When i create a PO the new output type is not getting proposed by the system. I am not sure why it is not getting porposed in the message control.
I tried to manually enter the ZNEU output type in the system to see if the system is accepting. I am getting an error
Partner % does not exist for partner function LS
Any idea what i am missing? Am i missing any configuration or am i doing something wrong?
cheers

The output is not being proposed automatically is becuase you are missing "Condition Records" for the output type ZNEU.
Go to NACE.
Select EF - Purchase Order
Select "Condition Records"
Select ZNEU and select condition records
Now, system will bring the combinations of access sequence. Maintain appopriate record.
This will enable you to get the output type automatically in the purchase order.
Regards,
Naimesh Patel

Output type not getting defaulted in PO

Hi.....
I have configured output type as printout for purchase order, i have set the default value for message type NEU, even than when i create a PO system is not picking the message type NEU..
i have also mainatined condition record in MN04 for the purc. document type..
any other setting need to be maintained....
Kindly suggest....
Regards
Sarfraz

Hi,
Please check the following
1. Condition Table
SPRO > Material Management> Purchasing -> Message -> Output Control->Condition Tables->Define Condition Table for Purchase Order
Select:
Purchasing Doc. Type,
Purch. Organization,
Vendor
2. Access Sequences
SPRO -> Material Management-> Purchasing -> Message -> Output Control->Access Sequences->Define Condition Table for Purchase Order
3. Message Type
SPRO -> Material Management-> Purchasing -> Message -> Output Control->Message Types->Define Message Type for Purchase Order
Copy NEU to ZNEU or YNEU
4. Message Determination Schemas
4.1. Message Determination Schemas
SPRO -> Material Management-> Purchasing -> Message -> Output Control->Message Schema->Define Message Schema for Purchase Order-> Maintain Message Determination Schema
4.2. Assign Schema to Purchase Order
SPRO -> Material Management-> Purchasing -> Message -> Output Control->Message Schema->Define Message Schema for Purchase Order-> Assign Schema to Purchase Order
5. Partner Roles per Message Type
SPRO -> Material Management-> Purchasing -> Message -> Output Control-> Partner Roles per Message Type ->Define Partner Role for Purchase Order
6. Condition Record
Navigation Path: SAP Menu-> Logistics -> Material Management -> Purchasing-> Master data->Messages-> Purchase Order-> MN04-> Create
Now you create PO (ME21N) and save it. Go to ME22N and print the PO by giving output type ZNEU or YNEU.
G.Ganesh Kumar

Tax condition(JVAT) of ship to party is not triggering in Sales order

Hi,
Tax condition(JVAT) of ship to party is not triggering in sales order...
Scenario:
Tax condition types:
JCST- CST Payable
JVAT- VAT Payable GJ
Customer Tax classification for JVAT in OVK3:
1- VAT 4%
A- VAT 0%
B- VAT 2%
Material Tax classification for JVAT in OVK4:
0-Tax Exempt
1-Full Tax
In CMR for
Sold to Party:1001(Mumbai), In Sales Area Data(Billing Tab),we have
Country/Name/Tax category/Name/Tax Class./Descrption
IN / INDIA / JCST / CST Payable / 1 / CST 3%
IN / INDIA / JVAT / VAT Pay GJ / 1 / VAT 4%
In CMR for
Ship to Party:2001(Gujarat),In Sales Area Data(Billing Tab),we have
Country/Name/Tax category/Name/Tax Class./Descrption
IN / INDIA / JCST / CST Payable / 1 / CST 3%
IN / INDIA / JVAT / VAT Pay GJ / A / VAT 0%
Access Seq: JLST
Condition table : 368(Country/Region of Del Plant/Region/Tax class1-Cust/Tax Class1-Mat)
Condition record maintained for JVAT as IN/GJ/GJ/1/1 as 4%
Condition record maintained for JVAT as IN/GJ/GJ/A/1 as 0%
Now the sale(Shipping to) is happening in Gujarat..
In sales order
I entered SP:1001 and SH: 2001
When i check the pricing in sales order,condition type JVAT is triggering 4% which is not true as it as to pick 0%
Kindly guide me where i went wrong...
Regards
Azeez.Mohd

Hi Friends.
I found the solution...
Its customization mistake..
Solution:
When we have 'n' tax categories then we should have 'n' condition tables..
I have 2 tax categories: JCST and JVAT but i have only one condition table 368 which is wrong.. i should have 2 condition tables.. so i created another con. table 468 and assigned to access aeq JLST.
then when i create cond. record , we have to select the appropriate table then it will fetch accordingly.. in sales order..
with regards

PO Output Type not picked

Dear Experts ,
I have defined a new condition table for PO o/p as Doc Type/P Org/Vendor/Plant.
I assigned this table to the access seq
& the acces seq to the output type .
Then I maintained Condition record for this acces seq
But the output tupe is not getting picked in the PO
The analysis shows the message Access Not Made (Initialized Field) .
Also I not that the system cannot pick the value of plant from the PO .
to solve this I ticked the "Initialize" tick box in the access field WERKS.
now the message is gone , but still the o/p type doesnt pick.
please sugges if this is possible at all ( I have doubts as the plant is an item level field in PO ) . If yes how .
Regards
Anis

Dear Anis,
If output type is triggered with txn like ME9F, then you can get data from EKPO table itself. Otherwise you can use options.
1. Export item data from some userexit or BADI (ME_PROCESS_PO_CUST) to memory id and then get that data in userexit userexit_komkbea_fill.
2. Using field symbol, you can get the data in userexit userexit_komkbea_fill from memory.
Data : W_Text(30) type C
Fields symbols : <FS> type EKPO.
w_text = '(Program name)EKPO[]'.
Assign w_text to <FS> .
Kind Regards,
Suneet

Output type not triggered during Delivery Order - pls help

Similar Messages

Maybe you are looking for