Multiple output records for delivery type access order sequence

Hello,
This is a question about output delivery type for outbound deliveries.
I have created one delivery type YF and two output condition types YDL1 and assigned access sequence (by sales org/customer) and YDL2 (by shipping point) in NACE V2 shipping. I have also created their corresponding condition records: salesorg/cust and shipping point in VV21.
When I created my outbound delivery YF from sales order and saved it. System finds both output condition types. First YDL1 and then YDL2 as expected because condition records have been maintained. However, I need to change this order so that YDL2 is the default one and YDL1 is found next.
Could somebody help me how do I change this order?
Thank you in advanced.

Hello,
what do you mean with
I need to change this order so that YDL2 is the default one
When two or more output types are determined, they have the same "rank".
If you mean that you want to sort the output types to have one printed before the other one, please refer to point 3. of OSS Note 960611
https://websmp130.sap-ag.de/sap(bD1pdCZjPTAwMQ==)/bc/bsp/sno/ui_entry/entry.htm?param=69765F6D6F64653D3030312669765F7361…
Best regards,
Andrea

Similar Messages

Multiple results recording for Delivery inspection lot

Hi Gurus,
My requirement is to configure for quality results recording for sales delivery document. Where client wants to record Customer, supplier, Umpire, etc results record for inspection characteristics.
I got response from few Sapiens that I should use Inspection point concept for multiple results recording. Could anyone cna tell me how can I do this.
Your help will be highly appreciated.
Thanks,
Kumar

Hi Kumar,
Okay!
First of all letu2019s try to understand whether inspection points are really suitable for your requirement or not. Accordingly further errors can be eliminated. I just try to understand.
A- Using Inspection Points
1.     Inspection points are used when you inspect the same parameters again and again.
2.     When you click on results tab in QA32, system asks you put some identification number. Letu2019s say you put A1 and then press enter. Thereafter you record the actual results (LENGTH, WIDTH etc.) You save this without giving UD.
3.     For the next time when you again click on results for the same inspection lot, system again asks you to put identification number. This time suppose you put A2. Then again you record the results (LENGTH, WIDTH) for A2.
4.     Likewise you can retrieve the inspection results from system with respect to inspection point (identification point).
5.     Typically this can be used for chemical industries where you record the temperature of the same chemical after every ½ an hour. Here 10:00 am, 10:30 am can be used as identifications numbers. As a result of which you can get the information that at 10:00 am temperature was 40 Deg and at 10:30 am it was 75 degree Celsius.
If your requirement resembles this situation, then only the use of inspection points would be fruitful.
B- Without Inspection Points
But if you want to record the readings by various agencies like customer, umpire (refer following pattern)and want to compare them there are other ways.
1.     Reading by your inspector
a.     LENGTH u2013 100, 101, 102mm (average is 101mm)
b.     WIDTH     - 10.50, 10.50, 10.60mm (average is 31.6mm)
2.     Reading by customer
a.     LENGTH u2013 100, 101, 102mm (average is 101mm)
b.     WIDTH     - 10.50, 10.50, 10.60mm (average is 31.6mm)
3.     Reading by umpire
a.     LENGTH u2013 100, 101, 102mm (average is 101mm)
b.     WIDTH     - 10.50, 10.50, 10.60mm (average is 31.6mm)
You can achieve this without using inspection points also. For this in QP02 you need to create 3 operation; Inspector, Customer and umpire respectively. Feed the MICs in each of these operations. When you click on result tab system will throw pop up for these 3 operations. Double click on Umpire if you want to record results noted by umpire. Likewise for rest of the operations. You can do this even after UD also (after 1-2 months also). You need to use MIC with control indicator as long term characteristics for this in QS23.
Regarding averaging of results u2013 This can be achieved using single result recording MIC with or without inspection points. Use appropriate sampling procedure. When you feed results in QA32 system automaticaaly averages out the reading. This can be viewable against phi symbol.
Finally you did mention that u201Chere I am not getting the newly created inspection lotsu201D. Does that mean inspection lot (10 origin) has not created?
Regards,
Anand Rao

How to create a record for table PLAF with order type 'NB'.

How to create a record for table PLAF with order type 'NB'(standard purchase order).
who can tell me the T-code or some usefull information?
Thanks.

Hi
This will be updated automatically when generate planned orders thru MRP. (MD02)
regards
Srinivas

Automatic output assignment for delivery document

HI
Can any bady let me know the pre requisites for automatic output assignment for delivery document with reference of PO(stock transfer order)
As of now i configureded every thing fine, i add manually the output is working fine, and i created condition record also. only the things in this is
i need this output automatically when i save my delivery document
Regards,
Vadivel

Dear Vadivel,
Go to your delivery output procedure control data here you you keep Manual only check box as uncheck for your Replenishment delivery output type.
Also check the Requirement assigned to your Replenishment delivery output type.
I hope this will help you,
Regards,
Murali.

Multiple Output Medium for vendors in Manage Business Partner

Hi,
I'm trying to put more than one output medium in Manage Business Partner for a Vendor, Transaction BBPMAININT.
But unable to do so.
1. I would need assisstance that is it right to have multiple output medium for a Vendor functionally?
2. How do i achieve it.
Waiting for a quick response,
Regards,
Neha Misra.
Edited by: Neha Misra on Mar 28, 2008 1:18 PM

You can maintain Alternate Vendor Contact for the Vendors in the transaction BP; The Purchaser here after can choose which one to use during a particular time of the ordering the purchase order. This will be possible for the purchaser at the time of creating the purchase order in the Basic Data Tab - Alternate Vendor Contacts.
For every vendor contact you will need to have a default medium for output; which will be used to send the PO to the vendor.
Please reward points if found useful.
Thanks
Kasee Palaniappan

Import multiple info records for 1 material item in repository

Hi Guys,
I have got sort of a puzzle I can not solve at the moment, maybe some one can help me to solve it. The situation in our system landscape is as follows:
Systems:
SRM 5.0 (Classic implementation scenario)
ECC 6.0
SRM-MDM 2.0
PI 2005
Material master is maintained in R/3 and the materials are replicated to SRM. From SRM we replicate all materials to the catalog repository in SRM-MDM.
As the material master in R/3 is vendor independent, the materials replicated to SRM also have no vendor attached. For the first initial material replication from SRM to the catalog SRM-MDM this also means that the products in the main table of the repository, u2018catalog positionsu2019, will not have a vendor or vendor number attached (i.e. no reference to a source of supply).
To assign a source of supply in the repository to a product (record) we will use info records which are replicated from R/3 to SRM-MDM. The mapping for this in the Import Manager can only be based on the product number. As this is the only unique value available which can map a info record to a already existing (but vendor less) ptoduct item in the catalog.
As long as every item in the repository has only one unique info record, meaning one source of supply with a specific price, there is no issue in the above scenario. Based on the product-id, the info record data will be matched with the material item in the catalog.
The issue for me arises when multiple info records exists for the same material. The info records can heave different vendors and different prices. All possible vendors should be available in the catalog for the same material (at least this is the requirement ).
At this point the product-id will no longer be an unique value. Importing the info records will cause problems, as only one material record is available in the repository for the specific product-id (remember that when doing a initial replication of the material master to the catalog, no vendor data is replicated).
Does anyone had this issue before, and knows a solution? Is it for example possible during the import of the info records in the Import manager, to duplicate material records in the destination data, based on the number of info records available in the source data for the same product-id. Or is there an other solution that I am missing?
Your help would be appreciated!
Regards,
Skander

Hi Shai & Ravi,
Thanks for your answers. The MDM version which we are using is 5.5 - currently on SP6
@ Shai: you are right; the standard SRM-MDM 2.0 catalog repository has a qualified lookup table u2018priceu2019, in which itu2019s possible to store the info record data. The standard fields in this sub-table are: Purchase Org, Amount, Currency Lower B, PIR-ID, price based quantity and Price based quantity UoM.
I added some extra fields (non qualified), to accompany the remaining info record data (product no. u2013 vendor id u2013 product category) which is exported/imported, via the standard extraction program in R/3: Tcode MECCM
I tried the solution Ravi proposed. This scenario works fine when, for example you want to maintain multiple info records for one specific material record in the main table (all info records related to the same source of supply, i.e. vendor). But as I described, the info records we import for one product can have different vendors.
The source of supply (vendor) in the shopping cart of SRM is determined via the u2018supplieru2019 field in the main repository table (which is in itself a flat lookup table ). What happens now is that all related info records are added to the u2018price informationu2019 field of the specific product record in the main table. Thus info records which have different suppliers are attached to a record in the main table which will have one specific supplier in the u2018supplieru2019 field. So from my point of view this will not work.
I am still stuck with the situation that the material master import will only import one record for every distinct product, which can have multiple info records. The info records can/will have different vendors. As the supplier field in the main table determines the source of supply in the shopping cartu2026. Iu2019am seeking for a solution which will duplicate the material records in the main table, based on the amount of imported info records for that specific material record, that have distinct vendors.
Shai, if you have some useful info on how you accomplished this requirement on a previous version of SRM-MDM, it would be greatly appreciated if you can share it..
Thx.
Skander

Standard data sources for Delivery and Purchase order quantity.

Hi gurus ,
Are there any standard data sources available for Delivery and Purchase Order quantity in Purchasing area .
Thanks in advance .

Hi,
If you are looking for SD Scenario: Check this : https://websmp201.sap-ag.de/~form/sapnet?_FRAME=CONTAINER&_OBJECT=011000358700002719062002E
Happy Tony

Not able to send Email in SOA Suite 12c,getting No matching driver found for delivery type = EMAIL

Hi All,
I am getting following Errror whlie Sending Testing Mail from Human Workflow .
No matching driver found for delivery type = EMAIL
I followed all the steps mentioned in blogs.
Steps that I followed--
1,Downloaded Gmail and Imap Certificate.
2.Imported in Keystore
3.Create a Email driver properties.
Than

Did you resolve this? I am running into the same problem. Not sure if it a configuration issue or an issue with 12c (go figure). I have tried both a blank sender address list and explicitly putting the target address in. Notification mode is set to email. I am using the Notification Test under Human Workflow/Notification Managent. Where else could it be trying to match the driver to EMAIL?
exception.type: ERROR
exception.severity: 2
exception.name: Error status received from UMS.
exception.description: Status detail :
Status type : DELIVERY_TO_DRIVER:FAILURE,
Status Content : No matching driver found for delivery type = EMAIL,
Addressed to : EMAIL:[email protected],
UMS Driver : null,
UMS Message Id : dcb01e3ec0a8456856fe8a439e6ecf3f,
Gateway message Id : null,
Status Received at : Mon Jan 12 00:49:27 EST 2015.
exception.fix: Check status details and fix the underlying reason, which caused error.
>

Vivado 2013.4 ERROR: [IP_Flow 19-395] Problem validating against XML schema: Invalid value format for this type spirit:order

Hello,
I just downloaded and installed Vivado 2013.4 on my Xubuntu 12.04 machine. But when I try to add IP from the IP catalog, as in the ug937 Lab1 step2, it fails with obscure error messages (see below).
Here's basically what I did:
-In the Flow Navigator, i select the IP Catalog button.
-In the search field of the IP Catalog, I type DDS.
-then I double-click the DDS Compiler and my error occure.
Please Help,
Jerome.
[HDL 9-1061] Parsing VHDL file "/home/jmassol/Desktop/Vivado/vivado_debug/ug937/project_xsim/project_xsim.srcs/sources_1/imports/ug937/sources/sinegen_demo.vhd" into library work ["/home/jmassol/Desktop/Vivado/vivado_debug/ug937/project_xsim/project_xsim.srcs/sources_1/imports/ug937/sources/sinegen_demo.vhd":1]
Analysis Results[IP_Flow 19-3378] Failed to create IP instance 'dds_compiler_0'. Error saving IP file.
[IP_Flow 19-193] Failed to save BOM file '/home/jmassol/.Xil/Vivado-2683-ubuntu/coregen/dds_compiler_0/dds_compiler_0.xml'.
[IP_Flow 19-193] Failed to save BOM file '/home/jmassol/.Xil/Vivado-2683-ubuntu/coregen/dds_compiler_0/dds_compiler_0.xml'.
[HDL 9-1061] Parsing VHDL file "/home/jmassol/Desktop/Vivado/vivado_debug/ug937/project_xsim/project_xsim.srcs/sources_1/imports/ug937/sources/sinegen.vhd" into library work ["/home/jmassol/Desktop/Vivado/vivado_debug/ug937/project_xsim/project_xsim.srcs/sources_1/imports/ug937/sources/sinegen.vhd":1]
[IP_Flow 19-194] Failed to save IP instance 'dds_compiler_0'.
set_property target_language Verilog [current_project]
[IP_Flow 19-193] Failed to save BOM file '/home/jmassol/.Xil/Vivado-2683-ubuntu/coregen/dds_compiler_0/dds_compiler_0.xml'.
[IP_Flow 19-193] Failed to save BOM file '/home/jmassol/.Xil/Vivado-2683-ubuntu/coregen/dds_compiler_0/dds_compiler_0.xml'.
[IP_Flow 19-395] Problem validating against XML schema: Invalid value format for this type spirit:order
[IP_Flow 19-194] Failed to save IP instance 'dds_compiler_0'.
[IP_Flow 19-395] Problem validating against XML schema: Invalid value format for this type spirit:order
sources_1[IP_Flow 19-194] Failed to save IP instance 'dds_compiler_0'.
[HDL 9-1061] Parsing VHDL file "/home/jmassol/Desktop/Vivado/vivado_debug/ug937/project_xsim/project_xsim.srcs/sources_1/imports/ug937/sources/sinegen_demo.vhd" into library work ["/home/jmassol/Desktop/Vivado/vivado_debug/ug937/project_xsim/project_xsim.srcs/sources_1/imports/ug937/sources/sinegen_demo.vhd":1]
[IP_Flow 19-194] Failed to save IP instance 'dds_compiler_0'.
[IP_Flow 19-194] Failed to save IP instance 'dds_compiler_0'.
update_compile_order -fileset sim_1
[IP_Flow 19-193] Failed to save BOM file '/home/jmassol/.Xil/Vivado-2683-ubuntu/coregen/dds_compiler_0/dds_compiler_0.xml'.
[HDL 9-1061] Parsing VHDL file "/home/jmassol/Desktop/Vivado/vivado_debug/ug937/project_xsim/project_xsim.srcs/sources_1/imports/ug937/sources/fsm.vhd" into library work ["/home/jmassol/Desktop/Vivado/vivado_debug/ug937/project_xsim/project_xsim.srcs/sources_1/imports/ug937/sources/fsm.vhd":1]
[IP_Flow 19-3378] Failed to create IP instance 'dds_compiler_0'. Error saving IP file.
[IP_Flow 19-395] Problem validating against XML schema: Invalid value format for this type spirit:order
[IP_Flow 19-3378] Failed to create IP instance 'dds_compiler_0'. Error saving IP file.
[IP_Flow 19-395] Problem validating against XML schema: Invalid value format for this type spirit:order
[HDL 9-1061] Parsing VHDL file "/home/jmassol/Desktop/Vivado/vivado_debug/ug937/project_xsim/project_xsim.srcs/sources_1/imports/ug937/sources/fsm.vhd" into library work ["/home/jmassol/Desktop/Vivado/vivado_debug/ug937/project_xsim/project_xsim.srcs/sources_1/imports/ug937/sources/fsm.vhd":1]
[IP_Flow 19-395] Problem validating against XML schema: Invalid value format for this type spirit:order
[IP_Flow 19-3378] Failed to create IP instance 'dds_compiler_0'. Error saving IP file.
[HDL 9-1654] Analyzing Verilog file "/home/jmassol/Desktop/Vivado/vivado_debug/ug937/project_xsim/project_xsim.srcs/sources_1/imports/ug937/sim/testbench.v" into library work ["/home/jmassol/Desktop/Vivado/vivado_debug/ug937/project_xsim/project_xsim.srcs/sources_1/imports/ug937/sim/testbench.v":1]
[IP_Flow 19-395] Problem validating against XML schema: Invalid value format for this type spirit:order
[HDL 9-1061] Parsing VHDL file "/home/jmassol/Desktop/Vivado/vivado_debug/ug937/project_xsim/project_xsim.srcs/sources_1/imports/ug937/sources/debounce.vhd" into library work ["/home/jmassol/Desktop/Vivado/vivado_debug/ug937/project_xsim/project_xsim.srcs/sources_1/imports/ug937/sources/debounce.vhd":1]
[IP_Flow 19-193] Failed to save BOM file '/home/jmassol/.Xil/Vivado-2683-ubuntu/coregen/dds_compiler_0/dds_compiler_0.xml'.
[IP_Flow 19-2313] Loaded Vivado IP repository '/opt/Xilinx/Vivado/2013.4/data/ip'.
[IP_Flow 19-395] Problem validating against XML schema: Invalid value format for this type spirit:order
[IP_Flow 19-3378] Failed to create IP instance 'dds_compiler_0'. Error saving IP file.
[IP_Flow 19-1704] No user IP repositories specified
[IP_Flow 19-194] Failed to save IP instance 'dds_compiler_0'.
[IP_Flow 19-193] Failed to save BOM file '/home/jmassol/.Xil/Vivado-2683-ubuntu/coregen/dds_compiler_0/dds_compiler_0.xml'.
[IP_Flow 19-3378] Failed to create IP instance 'dds_compiler_0'. Error saving IP file.
Vivado Commands[Project 1-11] Changing the constrs_type of fileset 'constrs_1' to 'XDC'.
[IP_Flow 19-193] Failed to save BOM file '/home/jmassol/.Xil/Vivado-2683-ubuntu/coregen/dds_compiler_0/dds_compiler_0.xml'.
[IP_Flow 19-3378] Failed to create IP instance 'dds_compiler_0'. Error saving IP file.
[IP_Flow 19-193] Failed to save BOM file '/home/jmassol/.Xil/Vivado-2683-ubuntu/coregen/dds_compiler_0/dds_compiler_0.xml'.
sim_1[IP_Flow 19-194] Failed to save IP instance 'dds_compiler_0'.
[IP_Flow 19-395] Problem validating against XML schema: Invalid value format for this type spirit:order
[HDL 9-1654] Analyzing Verilog file "/home/jmassol/Desktop/Vivado/vivado_debug/ug937/project_xsim/project_xsim.srcs/sources_1/imports/ug937/sim/testbench.v" into library work ["/home/jmassol/Desktop/Vivado/vivado_debug/ug937/project_xsim/project_xsim.srcs/sources_1/imports/ug937/sim/testbench.v":1]
[IP_Flow 19-395] Problem validating against XML schema: Invalid value format for this type spirit:order
[IP_Flow 19-3378] Failed to create IP instance 'dds_compiler_0'. Error saving IP file.
[IP_Flow 19-234] Refreshing IP repositories
[IP_Flow 19-3378] Failed to create IP instance 'dds_compiler_0'. Error saving IP file.
[IP_Flow 19-395] Problem validating against XML schema: Invalid value format for this type spirit:order
[IP_Flow 19-194] Failed to save IP instance 'dds_compiler_0'.
[IP_Flow 19-193] Failed to save BOM file '/home/jmassol/.Xil/Vivado-2683-ubuntu/coregen/dds_compiler_0/dds_compiler_0.xml'.
[IP_Flow 19-194] Failed to save IP instance 'dds_compiler_0'.
[IP_Flow 19-395] Problem validating against XML schema: Invalid value format for this type spirit:order
[IP_Flow 19-193] Failed to save BOM file '/home/jmassol/.Xil/Vivado-2683-ubuntu/coregen/dds_compiler_0/dds_compiler_0.xml'.
[IP_Flow 19-194] Failed to save IP instance 'dds_compiler_0'.
[IP_Flow 19-3378] Failed to create IP instance 'dds_compiler_0'. Error saving IP file.
[HDL 9-1061] Parsing VHDL file "/home/jmassol/Desktop/Vivado/vivado_debug/ug937/project_xsim/project_xsim.srcs/sources_1/imports/ug937/sources/debounce.vhd" into library work ["/home/jmassol/Desktop/Vivado/vivado_debug/ug937/project_xsim/project_xsim.srcs/sources_1/imports/ug937/sources/debounce.vhd":1]
[IP_Flow 19-3378] Failed to create IP instance 'dds_compiler_0'. Error saving IP file.
[IP_Flow 19-194] Failed to save IP instance 'dds_compiler_0'.
[HDL 9-1061] Parsing VHDL file "/home/jmassol/Desktop/Vivado/vivado_debug/ug937/project_xsim/project_xsim.srcs/sources_1/imports/ug937/sources/sinegen.vhd" into library work ["/home/jmassol/Desktop/Vivado/vivado_debug/ug937/project_xsim/project_xsim.srcs/sources_1/imports/ug937/sources/sinegen.vhd":1]
set_property constrs_type XDC [current_fileset -constrset]

We had the same problem when switching to Ubuntu 14.04, and there actually is a solution for it: make sure your locales are set to English.
$> env | grep LC_*
should only show english (or C) locales, all others are known to cause parsing errors in some numbers, usually caused by wrong string-to-float conversions (e.g. 18,29 in german is 18.29 in english). You can change the locales in the file /etc/default/localesThis is not the first time we had problems with the locale settings, Xilinx does not seem to test their software with anything else than en_US, causing obscure bugs like this one.
HTH
Philipp

How to get multiple output formats for each execution of the report?

Hi,
Is it possible to get multiple output formats for each execution of the report? If so can you provide some details?
Thanks

In Reports 6i, Reports Distribution was introduced. This allows you to run the report once and output to a number of destinations with a different format. It also allows you to distribute individual sections within a report to different destinations in different formats.
The Destinations for a Report to distribute to are defined either in a distribution file and passed on the command line or inside of the report definition.
To add a destination to the the report definition, bring up the property palette against the report object and then select the "Distribution" property under the "Report" node. This will bring up a dialog that allows you to create a distribution list. You can then test this list by selecting "file->distribute" from the menu.
To run a report that is to be distributed through rwrun60, you need to add "distribute=yes" to the command line. It will pick up the destinations from the report definition. If you add "destination=<filename>" then it will pick up the destinations from the specified "<filename>" and ignore the destinations in the report definition.
Note: if "distribute=yes" is specified on the command line then the destype/desname/desformat parameters will be used to format the report (ie: which printer/display to use during formatting for sizing objects) but will be ignored when the report is sent to the destinations.

Multiple output/action for ECS Purchase Order

Hi,
We have a business scenario where; for a particular plant, the purchasing department would like a printed copy of the Purchase Order at the time the PO is issued via email to the supplier. I've tried setting up dual processing types (ie. Print&Mail) but I cannot find the PO parameters required (ie. Plant) within the business object BUS2201 to create the appropriate schedule or start conditions.
Am I going about this the right way? I would prefer to stay away from the suggested R/3 output approach from note 883693.
We are using Extended Classic Scenario in SRM5.0 (Server5.5).
Assistance would be greatly appreciate.
Kyle.

you can use the BBP_PO_ACTION_CONF (or something like that) transaction to create multiple output in SRM.
If the fields you need are not available in BUS2201, you can create your own delegate of BUS2201 and retrieve those parameters yourself in the custom ZBUS2201.
Regards,
Robin

Delivery Output determiantion using Delivery type & Item category

Dear all,
I am facing a problem while triggering output using Delivery type/Item Category access in access sequence xyz. I have maintained the condition record for this access and did all the necessary customization settings.
When i maintain the condition record for other access in Access sequence xyz the out put is being triggered.
After some analysis i found that the Delivery type/Item category is using different communication structures.
ie. Delivery type is using KOMKBV2-LFART. where as Item Category is using KOMPBV2-PSTYV. The output is a header output.
can any one explain the problem here in maintaining different comm structures for an access for generating header output.
Thanks in advance for your inputs.
Best Regards
Satish

Hi,
You mean to say its not triggering the output automatically.....
If that is the case then goto the condition type in IMG and in tab "default values" make the dispatch time as "send immediately when saving the application" this will automatically triggers the output based on the condition records.....
Regards
Bageerath

Output Determination for Delivery doc

Hi Friends,
I am not able to see any output types maintained for delivery documents.......LD00 is the output type for delivery..so whr the setup exists in IMG?.....thanks in advance.....

Hi
You can go to NACE t-code to check for your output type. On the main screen, select "Shipping" and click on "Output Types" icon on top.
Search for your output type say LD00. You will be able to see what is the driver program against it and what form (standard SAP or customized) is attached to it for printing purpose.
Go to VV23 T-code and input your condition type LD00 and click on "condition info" and execute it. You will be able to see what condition records are maintained against that output type. If you dont get any entries then condition records have to be maintained. For this you can go to VV21 T-code and maintain the condition type LD00 for printing against any access sequence available in your system.
Hope this helps
Regards,
Syed Nasir

Conditon record for condition type

Hi
i create my condition record for my condition type( pr00, MWST,) in pricing in vk11 but when i create my condition type for output type, account determination and text determination i don't create the condition record in vk11 so how is itpossibile
Vinz

Hi Vinz,
For Account determination in SAP, Condition Technique is used. First we Create condition tables. Then we create the key combination/Access sequence(Sequence of condition tables created), then we create condition types(We have two standard condition types-- KOFI(With out controlling and KOFKWith Controlling). We assign these Condition types to the Procedure and the procedure is assigned to the billing types. One of the combinations is " Application/sales org/chart of accounts/ condition type/acount assignment group of customer/acct assign group of mat/ account key/gl account."This combination is nothing but access sequence and this is assigned to a condition type. In "VKOA" we specify the system whats the G/L Account to be picked up. This acts as a condition record. Account keys are assigned to each condition type in pricing procedure. Based on the account key of particular pricing condition type(Ex: PR00ERL) ,system will pick up the respective condition type from "VKOA". Kindly please let me know If you need any more Information on this,
Regards,
Ram Pedarla
Edited by: RamPedarla on Mar 17, 2010 5:59 PM

Output determination for shipment types

Hi SD gurus,
I am new to SAP. I am unable to configure o/p for shipment documents. I wanted to send an EDI to carrier when my planning is done and email to customers when loading takes place. an some1 help me through this.
Thanks in advance.

Dear VGR,
Do the configuration settings for the shipment output determination through this IMG path
IMG>Logistics Execution>Transportation>Basic Transportation Functions>Output Control-->Maintain Output Determination for Shipments
-->Maintain Condition Tables
-->Maintain Output Types
-->Maintain Access Sequences
-->Assign Output Types To Partner Functions
-->Maintain Output Determination Procedure
-->Assign Output Determination Procedures
I wanted to send an EDI to carrier when my planning is done and email to customers when loading takes place.
For he above requirement you take help of ABAPer to develop the output program in such way and assign that program to your shipment output type.
Maintain the condition records through VV71 transaction with Transm. Medium EDI and Email
I hope this will help you,
Regards,
Murali.

Multiple output records for delivery type access order sequence

Similar Messages

Maybe you are looking for