Billing output controls
Hi,
Can any body could help me out fot this issue?.
1. Created a condition record via TC: VV31 for the key combination Plant/Billing type.
2. Condition record information is flowing while creating a Billing document (VF01) correctly. But the issue is after saving the billing document the condition record alone in the Header->output-> Does not have any data that means system not taking the data after saving the the billing document.
Hence I am not able to trigger any output automatically. Eventhough the system is not storing the condition record information in the Table : NAST. Table NAST is showing blank for the billing document.
Please give your valuable suggesting to get the required output record automatically after saving the billing document.
Thanks & Regards,
Vijay
Hi zKen,
Thanks for your reply.
We have added WERKS as a one of a key filed in the Output determination and complete entire coding by using User exit 'USEREXIT_KOMPBV3_FILL' and all the procedures done step by step.
After this as per my Access sequence the condition records (key combination is Plant/Billing type) are flowing into Billing (VF01) perfeclty. But after save the billing if you go to VF03 you can not see anything under Header>Output>Communication.
So nothing has been saved, but it's fetching the condition record perfectly. This is an issue and the print is not trigerred automatically.
Can you please help on this?
Regards,
Vijay
Similar Messages
-
I managed to do the configurations where I can print out an invoice in a certain format which I maintained for output type RDXX. So, I go to VF03, insert the invoice number then go to path Issue output to ---> RDXX. Then print.
The problem rises when I try to print out a different invoice. The RDXX is not there. How to set that RDXX is available for every invoice i want to print out?hi
If i got ur point correctly u don't want to manually enter the condition . U want it should flow automatically .
For that in NACE Tcode or goto Spro-> Img->SD -> Basic function -> output control . Goto ur output procedure , double click on it . Goto ur condition type i.e RDXX in that please uncheck the check box saying Man( Manual) .
This will help to flow this condition automatically . -
EDI billing outputs are capturing credit memos as well as invoices
I am a newcomer to the company I am currently with, and to this forum, and I have 6 years of experience in EDI and SAP SD.
I am working on a project to determine why our EDI billing outputs are capturing credit memos as well as invoices, and attempting to send them by EDI, causing failures in our Seeburger translator. Most customers donu2019t want credit memos by EDI. My goal is to track backwards and determine what portion of the EDI process in SAP is pulling credit memos rather than just invoices. I suspect that someone intentionally made changes in the past to put this in place, but we need to have a message type that includes invoices and credit memos, to be attached to specific partners that want this, and another more standard message type that sends only invoices.
The message control for the example partner specifies Message Type ZURH (customized by this company for some reason), Application V3 (which seems standard), and process code SD09 (which seems standard). Could someone help me to navigate to an area where I may be able to find out what parameters are used to determine what transaction types are pulled to be sent out by EDI for billing? I suspect that the issue may be in Application V3, but I am unable to find any help to view u2018Applicationsu2019, because application is such a widely used word.
How can I display/change Application V3, in order to check itu2019s contents?
Any other ideas why credit memos may be included would be appreciated, and I always appreciate having the transaction codes mentioned as well.
Thank you in advance for your assistance.
Application V3 (what specifies what transaction type this pulls?)
Message Type ZURH,
Process Code SD09.
Access Sequence used is ZSD1 Billing Documents (Access Sequence ZSD1 does not appear in transaction V/48 (?))
Transmission Medium is 6 EDI.
The program is RSNASTED, and the FORM Routine is EDI_PROCESSING.Satish,
Thanks for the suggestions.
I checked transaction VV33 u201CDisplay Output Condition Records: Billingu201D for Output Type ZURH, Key Combination Sales Org/Payer, and I find the example customer linked to ZURH, as I would expect (5010013645 BEST BUY CANADA Vendor #41448 PY 6 1).
I donu2019t see any data about specific transaction types such as credit memos or invoices, so I may not be looking in the right place. I donu2019t find entries under any other key combination. How would I check if Output Condition records are maintained for credit memos?
In regards to the output type being assigned to the credit memo billing type (ZG2U), Iu2019m afraid I donu2019t know how to check that either.
In NACE, I see that u2018Proceduresu2019 list the CTyp (?), and procedure US0001 is the only one that includes credits and debits. I donu2019t recognize the Ctyps ZDN0 and ZCN0. The billing type is ZG2U, which I don't see in any of the Procedures:
10 1 RD00 Invoice
20 2 ZPRO Proforma Invoice
30 1 ZCAN Canadian Cust. Inv
40 1 ZCOM Commercial Invoice
50 1 ZDN0 Debit Note
60 1 ZCN0 Credit Note
How would I be able tell which u2018Procedureu2019 is being used for Application V3, and how would I change that to another Procedure for testing? -
Billing output to IDoc & reprocess the IDoc in same sys. to post FI entry
I have a requirement to send the billing output to IDoc, read the same IDoc to post a FI entry but to another company code. Please suggest how can this be acheived, and is there any other alternative to acheive the above requirement.
Thanks in advance.Hi Naga,
I have to select the records in JDBC based on different conditions each time. For example I have to select based on company code '1000' and Employee claasification 'E1' and date range. After I post these records in SAP again I want to select other records for some other company code '2000' and different business area and different dates. Basically I want to extract data multiple times based on different conditions.
-->
Such requirements cant be handle through select query of the sender...but you can handle this in the message mapping area.....you can fire a select query in the database to pick up records in a batch of 10K (do not keep any condition on this except for sorting). After the records come into PI you can send the message to your target based on the unique combination of "Company code+ Employee clasification + date range" handling this in the message mapping.
Another question is in the JDBC to IDOC scenario since the sender adapter is JDBC and the sender adapter polls depending on the duration of time ( say 60 secs ) in the adapter once after I extract the data based on a condition how do I control in such a way that the same data is not extracted again.
You can use the N--> C logic
The data records that you pick have a corresponding control table i assume. There should be a field STATUS where the initial status of record should be N.
After you pick the records this status should be made C so that only those records present in the database with status = N are picked up.
Mention the condition Status = N in the select query.
Thanks
Dhwani -
Hi ,
I have a requirement. Is that in the Output Determination can we control the specific ouput type for user specific.
I,e In billing output for output type "RD00" for the print medium 1, i need to control at user level. One user should be able to generate this output & the other user should not.
Please give me suggestion on the above. This should be only controlled through configurations but not through any Z Programs.
Points Rewarded.
Regards,
Chakri MDear Chakri,
As you mentioned that one user should have access for Output but the other should not have the same.
Please contact your basis or security team to give the access to the person whom you want authorisation for Output and check the other user whether he is having access to Output generation, If he have authorisation ask Basis team to deactive his authorisation.
If you have any concern revert back the same to me
Amjad -
Hi i am interested to know the configuration details for maintaining output determination.Pls send me any material to my mail id.
My id is:[email protected]
Thanks&ragardsHi Kishore Kumar,
OUTPUT DETERMINATION:
Output determination in sales and distribution allows you to control proposal using assignments and groupings in such a way that the system selects the output allowed in each sales transaction and carries out output processing according to predefined criteria.
In the SAP System there are two possible ways of controlling output determination for each output:
proposal of output from the customer master record
proposal of output using the condition technique
SAP recommends the output proposal using the condition technique. This is because it is much more flexible than taking the proposal via the customer master. For example, the condition technique makes it possible to determine the most suitable output from several different types of output.
Note
Output control occurs separately in the header and item levels.
The proposal of output for sales support outputs can only be carried out using the condition technique.
Hope you are aware of that the output determination is done for
1. Sales Activities
2.Sales Documents
3.Delviery
4.Shiping and Transportation
5.Billing
FOR Customization please follow below steps:
MENU ;- IMG --> Sale and Distribution --> Basic Functions --> Output Control -->
Output Determination --> Output Determination using Condition Technique :
Maintain Output Determination for Sales Documents :
1.Maintain Condition Tables
2.Maintain Output Types
3.Maintain Access Sequence
4.Maintain Output Determination Procedure
5.Assign the Output Determination Procedure.
Finally Create condition Record using the T.Code: VV11
Then Create the Sales Order and Save it and go to the same sales order in Change mode.
Here in Sales Order main Screen --> Click on Extras --> Output --> Header --> Click on Print Preview.
T.Code: NACE
Output Determination
Output is a form of media from a business to one of its business partners. The possible media forms are printouts, faxes, telexes, e-mails, and EDI. The output can be sent to any of the partners defined in the document. Outputs are usually in the form of order confirmations, delivery notes, invoices, and shipping notifications.
Output determinationOutputBasic fncsSDIMG
An output type is simply a type of output and it contains all the control features for the output. For ex, it defines the kind of output, which business transaction it applies to, which business partner receives the output, how the output is sent (the media), and the print program and SAP Script layout to use in formatting the output.
Output determination can be maintained as originating from the customer master record or as originating by using the condition technique.
Output proposal from the customer master record
Output proposal from the customer master record, Define outputOutput determinationOutputBasic fncsSDIMG
In this option one creates output types, such as BA00 (order confirmation). After creating the output type, one assigns the output type to an output procedure, such as DB0001. After the assignment of the output types to the procedure, the output procedure is then assigned to the customer account group. This is a simple procedure and results in the output that is placed on the customer master record being copied into the sales document.
Out put determination procedure
In SAP we can send the documents to respective partner functions through different transmission mediums. SAP uses condition technique to determine output t relevant partners with relevant transmission mediums.
Out put determination procedure has a integration with technical module, as ABAPers has to write SMART forms and FORMS to print the output , that SMART form output can be send to relevant partner function through relevant transmission mediums.
Out put determination procedure for order confirmation: (V/57)
a) Maintain condition table:
Path:
IMG
SD
Basic functions
Output control
Output determination
Output determination using the condition technique
Maintain out put determination from for sales document
Maintain condition tables
Maintain out put condition table for sales document
Here we define condition table
Ex: 007 order type (sales order types)
Save it
b) Maintain output types:
IMG
SD
Basic functions
Output control
Output determination
Output determination using the condition technique
Maintain out put determination from for sales document
Maintain out put types
Here we define out put types
Ex: AF00 -- Inquiry
AN00 quotation
BA00 Order confirmation
BA01 EDI odd response
KRMLCredit processing
LP00 -- Scheduling agreement
MAIL Internal message
RD03cash sales invoice
Choose BA00 copy it and rename as a MA00
click on details icon
click on display to change icon
then again choose MA00 click on details icon
Maintain data in general data tab
General data tab:
Access sequence: 0010(order type)
In IMG define access sequence and assign to the output type
Check access to conditions:
This indicator allows the system to read the condition records for output. If it is not been activated then system determines out put from customer master ex: By following out put determination procedure DB0001
Check cannot be changed:
This control specifies whether the out put can be changed or not
Ex: direct mailings can be changed during processing
Check multiple issuing:
This indicator allows the system to send the output multiply
Ex: sales order has been sent for 10 items again one item has been added to sales order so that business has to issue the new out put for sold to party with added line items. This indicator allows the system to send out put repeatedly.
Check partner independent out put:
During output processing when the indicator has not set then system allows only specific functions in specific partner functions
Dont write processing:
This indicator determines whether system has to write processing log for output
Default values tab:
Dispatch time:
Ex: send immediately: when carry the application this indicator determines when the output should be sent.
Transmission medium:
Ex: print out
Fax
Telex
Internal send
EDI
Simple mail
Special function
Events (SAP business workflow)
Distribution (ALE)
Tasks (SAP business work flow)
Specify the transmission medium through which the output should be sent. (Ex: print output)
Communication strategy
Specify the communication strategy if you want to send the output externally
A) Time tab:
Check timing: (Periodic job not allowed)
This indicator allows the system to carry out print program periodically.
B) PRINT NEXT TAB):
Print parameter: Ex sales org.
Specify the print parameter.
Click on mail title & Text control button under dialog structure.
Here we assign title for the mail along with relevant text Ex:-EN (English)
Processing routines control button under dialog structure.
Here we assign programs form routines & form that are written by ABAPER, they they various transmission mediums.
Ex; - Transmission medium shortest program form routine
1 print out RVADOR entry
Click on position function control button here we assign relevant partner function to relevant transmission mediums
EX: print out: SP (Sold to party)
C) Maintain access sequences:
Here we define Access sequence.
EX: 0010 & Assign the condition tables to this output.
D) Assign out put types to partner function:
Here we assign output types along with transmission mediums to relevant partner functions.
EX: Out put type Transmission medium
MA00 1
2
6
A
MAIL 7
E) Maintain output determination procedure:
Here we define output determination procedure
Ex: V10000 - Order output
V05000 - Inquiry output
V06000 - quotation output
V10001 - Cash sales output
Choose output determination procedure EX; V10000, copy it& rename it as MA0000
Assign output type MA00 by going control date section.
Save it.
F) Assign output determination procedures;
Allocate sales document Header.
_ Choose sales document type OR & Assign output determination procedure i.e MA0000 & Assign output type MA00.
Assign sales document items.
-Choose item category TAN & Assign output determination procedure Ex: Ma0000
- save it & exit.
Maintain output records (vv11)
Path:
Logistic > S&D > Master data > output > sales document > VV11 Create
Specify output MA00, Click on Key combination & specify sales document type (OR), partner function (sp) transmission medium (1) dispatch type (4) language (EN)
Click on communication button on application tool bar
Specify output device LOCL or LP01
Check print immediately check release after output
Save it
Go to Va01 raise the sales order
Go to extra button output header edit.
Specify output type: MA00 partner function
Select line, click on communication methods
Specify logical destination
Check print immediately
Check release after output
go back save it & exit
Go to VA02, Go to Extras output header print preview
Check out (order confirmation )
Please Reward If Really Helpful,
Thanks and Regards,
Sateesh.Kandula -
Hello SDNs,
I have a requirement to send the billing output directly to the customer(BP) who is receiving billing document but it should be specific customers. Can you please explain where do we maintain for automatic billing output through customer email.
I have maintained transmission medium as email at billing output type level and maintained output codition record level.
Outout is not triggering as i have maintained above settings. Can you please guide the steps for getting output through email.
Regards,
KHi,
If you want to sent email to the BP the invoice copy then create your output type in SPRO>SD>Basic Functions>O/P control>O/P determination>O/P determination using condition technique>maintain Output Determination for billing documents.
Select RD00 and create an output type of your own. In the Default values tab maintain transmission medium "5" and partner function "BP" and Communication Strategy "CS01". Now at left side "Dialog structure " Maintain the values for each one
In the processing routines maintain medium "5" .Your program ,form routine and form.Also type "2 PDF".
In partner functions Maintain medium "5" and partner function "BP" these are the configurations when you maintain the new output type.
After creating the new output type maintain the same in output determination procedure. with Step/Output type (created by you).
Maintain the email address in customer master of BP.
Also check in SCOT to ensure the email is triggered -
Delivery Output & Billing Output
Hi All,
Are there any standard transactions for Delivery and billing ouputs, other than VL02N & VF02
So that user can view and take print outs of only those documents.
Thanks & Rgds
NaveenHi Naveen
DELIVERY OUTPUT:
VL71 Output from Outbound Deliveries
VL74 Output from Handling Units
VL70 Output From Picking Lists
VL75 Shipping Notification Output
FOR GENERAL TRANSACTION CODE REFER BELOW:
VL02N Change delivery document
VL04 Delivery due list
VKM5 List of deliveries
VL06G List of outbound deliveries for goods issue
VL06P List of outbound deliveries for picking
VL09 Cancel goods issue
VT02N Change shipment
VT70 Output for shipments
BILLING:
VF02 Change billing document
VF11 Cancel Billing document
VF04 Billing due list
FBL5N Display Customer invoices by line
FBL1N Display Vendor invoices by line
Create delivery via transfer orders
Once the order is saved proceed through the following steps. The process assumes the item has values in the warehouse bin.
VL04 Delivery due list. Run the delivery due with your order number to create the delivery
LT03 Create Transfer Order. EG. Warehouse: 101 and enter. Picking background. Save
The Transfer order should now be saved. It now needs to be confirmed.
In LT03 go to menu option Transfer Order -> Confirm Transfer Order
Enter
Save
The transfer order is now confirmed.
VL02N Delivery change. EG: Edit the delivery to do the following Pack External customer material number = COO. External delivery number Waybill number. BOL Transport tag. Carrier Header partner SP (E.G. FXP). Tracking number = Packing Unit
FOR ALL THE REQUIREMENT:
Transactions
search_sap_menu - Finds the menu path to a transaction - Can either type in TX code in the search criteria or a description- ie. 1st try SE38 and then ABAP.... the returned result is 'bottom to top'.
EDI Specific Transactions
VOE1 Translation between EDI categories and SD item categories
VOE2 Table EDSC view. Customer link to sales area detail
VOE3 Table view EDPVW. Add partner types that will be transferred to the IDoc
VOE4 Table view EDPAR. Link external partner number with our internal number
WEDI EDI Administrator Menu
BALE Idoc Administration
Scheduling agreements
OVA9 Create entries for each sold-to customer for which you will receive EDI schedule releases. At implementation, the only field that needs to be maintained is "Check PO number," which causes SAP to make sure that the PO number sent on the release matches the PO number on the schedule agreement. This transaction updates table T663A. SAP will not post an EDI schedule release, if this record is missing.
OVAI Create entries for each Vendor / Partner description combination. (Vendors must match sold-to Acct. at Cust., and Partner descriptions must match ship-to Partner descriptions.) This transaction updates table T661W. SAP uses this table to determine the schedule agreement sold-to partner.
OVAJ If you would like SAP to post schedule requirements using discrete dates only, instead of weekly and/or monthly buckets, you can indicate the days of the week that you deliver to this customer. SAP will divide the customer's quantity for a week or month evenly into the days of the week specified by the distribution function code. This code must be sent in the DELINS IDoc in field E1EDP16-ETVTF.
IDoc Transactions
WE09 / WE02 IDoc lists according to content. View IDocs via specific IDoc number or business application detail contained within the contents of a segment.
WE05 View IDocs
WE19 EDI test tool. Use to test inbound Function module changes.
WE20 Partner profile configuration. Add partner detail together with inbound and outbound relationships. We also incorporate message control on the outbound IDocs. Utilize the organizational units to trap functional errors for further processing
WE30 Create IDoc extension type
WE31 Segment create
WE57 Assign function module to logical message and IDoc type
WE60 IDoc type documentation tool
WE82 Link Release detail to Extension IDoc Type
BD55 Conversion rule user exit. Link conversion rule user exit to the different system \ partner combinations
BD87 Reprocess IDocs in error or waiting for action. (Both inbound and outbound in 4.6. Use BD88 in prior versions)
BALA ALE Application Distribution
BALM ALE Master Data Distribution
Output determination
856 - ASN
V/36 Maintain output determination for deliveries (Output determination procedures). V10000 (Header output) has condition type LAVA (usually with requirement 1 NB: Use V/84 V7ALLE SHAD for grouped ASNs. I.e. Group deliveries into shipments
VV21,VV22,VV23 Create output condition records for shipping. LAVA WE (Partner function) - We must add each new partner with VV21
VL71 Reissue output for deliveries
810 - Invoice
V/54 Maintain access sequence for billing documents
VV31,VV32,VV33 Create condition records for billing documents. (RD00 RE Billing party)
VF31 Reissue output for billing documents
855 Order Response
V/30 Sales document output types (BA00)
V/48, V/32, V/43 Maintain access sequence for sales documents
VV11,VV12,VV13 Create condition records for sales documents. (BA00 SP Sold to party)
Requirements coding
V/27 Create code to check requirements for output control. Used to check ZBA0 against BA00 output.
Sales & Distribution
Sales order / Quote / Sched Agreement / Contract
VA02 Sales order change
VA05 List of sales orders
VA22 Quotation change
VA32 Scheduling agreement change
VA42 Contract change
Billing
VF02 Change billing document
VF11 Cancel Billing document
VF04 Billing due list
FBL5N Display Customer invoices by line
FBL1N Display Vendor invoices by line
Delivery
VL02N Change delivery document
VL04 Delivery due list
VKM5 List of deliveries
VL06G List of outbound deliveries for goods issue
VL06P List of outbound deliveries for picking
VL09 Cancel goods issue
VT02N Change shipment
VT70 Output for shipments
General
VKM3, VKM4 List of sales documents
VKM1 List of blocked SD documents
VD52 Material Determination
Workflow
SWEAD Event queue administration
SWE2 Event type linkages
SWE3 Event linkages
PPOME Organizational Unit Maintenance
SWE5 Consistency Checks for Event Linkages
SWUD Workflow Diagnostic Tool
General
The following section provides detail on other useful SAP areas.
Create delivery via transfer orders
Once the order is saved proceed through the following steps. The process assumes the item has values in the warehouse bin.
VL04 Delivery due list. Run the delivery due with your order number to create the delivery
LT03 Create Transfer Order. EG. Warehouse: 101 and enter. Picking background. Save
The Transfer order should now be saved. It now needs to be confirmed.
In LT03 go to menu option Transfer Order -> Confirm Transfer Order
Enter
Save
The transfer order is now confirmed.
VL02N Delivery change. EG: Edit the delivery to do the following Pack External customer material number = COO. External delivery number Waybill number. BOL Transport tag. Carrier Header partner SP (E.G. FXP). Tracking number = Packing Unit
Purchase Orders
ME22N PO Change
ME57 Create PO from purchase requisition
Goods Movement
MIGO Post goods receipt
Other
MD04 Material Requirements. Shows material requirements and releases against materials
SE38 ABAP Editor. Used to modify ABAP programs
SM01 Transaction list. Lock transactions in the system. Also a good tool to see what transactions are available
SHDB Transaction recorder (BDC)
CMOD User exit \ project tool. Coordinates your changes into projects for the purpose of activating all user exits for a particular project. A user exit needs to be modified before it will work
SE16 Table contents display
SOST View mails sent externally from SAP
SU53 Check authorization object
SQVI Table Quickviewer Used to created quick client dependent reports
ST22 ABAP Dump Analysis
ST01 System trace
ST11 Display developer trace
ST05 SQL Trace
SM21 System log
ST22 Display short dumps
SM12 Display locked entries
Programs
List of ABAP Reports
Idoc
RBDAPP01 Post inbound Idocs to application documents
RBDAGAI2 Re-processing of IDocs after ALE input error
RBDAGAIE Reprocessing of edited IDocs
RBDMANIN Start error handling for non-posted Idocs
RSEINB00 Idoc inbound processing by file
RSEOUT00 Process outbound IDocs
General
RV80HGEN Report 'RV80HGEN' for including customer-specific routines in the SAP standard source code is not included automatically as an XPRA in the object list of the transport request. See OSS note 0385067. This report needs to be run in target clients once you have implemented a custom requirements definition.
RSWUWFML Report that interrogates the Workflow inbox, based on certain selections, and then forwards a notification to the respective users that they have email waiting in the SAP system. The auto-forwarding assignment of an email address to a user can be accomplished by the administrator and tx: SO36 or by the user themselves using tx: SO13. Use tx: SOST to view email status' sent from SAP.
RHSOBJCH Corrects the following error in workflow customizing:
Transport object PDST
Information Table SOBJ is consistent as regards key tables
**Error** Table HRP1600 Not an entry in table SOBJ
Information Table SOBJ is consistent as regards PAD tables
See note 134311 (point 2). Note 60801 also recommends the same steps regarding RHSOBJCH.
RSPO0075 Run report RSPO0075 to activate access method M for device types.
Reward if useful to u
Message was edited by:
narendran vajravelu -
Access sequence requirement for output control
Hi!
I would like to get some inputs on how access requirement for output control works. I created a new requirement for a condition table that has key combination billing type/sales org/country because I need to restrict the output for a paticular customer in one country. I think the requirement works fine such that it is not fulfilled for the customer that I want ot restrict, thus no output is created. However, I noticed that other customers in that sales org/country are affected by the requirement. The output is created (sy-subrc=0) but it is not processed (remains in yellow status). The output should be emailed immediately upon creation (medium 5/timing 4). For other sales org/countries the creation of output and sending of email work as expected.
I hope someone have valuable inputs regarding this.
Note: I created this discussion under ABAP development but it was rejected, for reason: This does not appear to be an ABAP question. So I hope I have selected the correct one with SD.
CholenThere is Output determination log available in the output screen (see the menu). It tells everything about how the output was proposed.
If the requirement is not fulfilled, you won't see output created with any color - yellow, red or purple with sparkles. If output has been proposed and has a yellow light it means it has not been processed yet. Output is processed only after the document has been saved, so while creating the document, you'll never see any other color. If after saving the document output is still yellow, it must have a different timing than 'process immediately' and it will be processed according to that setting.
This is a very simple concept, well documented and discussed gazillion of times on SCN. Requirements and conditions are two different things with different purposes. You might want to read a bit more on the output determination.
Thank you. -
Emailing functionality for billing output
Hello SDN's,
As per requirement, business needs to send invoice output to customer email directly and business needs to validate the invoice before sending to customer email .Can you please suggest how do we implement this process in as per business requirement.
I have checked current functionality, as per that business is validating the invoice before sending to customer(not email).
Please suggest.
Thanks in advance
Regards,
KVHello Guru's
Based on the discussion, I do have similar business requirement but with little twist, as it can never be same
I need to configure billing output via ale. which they want in email format to be sent to vistex for further processing.
Secondly this output has to be for some special customers, business will run a batch by the end of the day to push this docs for further processing to vistex.
So for this solution do I control it by output routine or maintain access sequence?
And also which transmission medium should I use?
Please suggest on this.
Thanks
Aman -
Generate XML file from Billing Output
Hello,
We have a business requirement to generate XML file from billing output and the same needs to send to external system for document printing. In this regard, could you please guide the steps to configure or share the document on how the system to be configured to support the XML file generation from billing document.
Anticipating a positive reply
Thanks in advance
Best Regards,
Gouthamanother option is to configure an outbound IDOC and set the port for this IDOC to generate an XML file.
here again there will be IDOC control record in the first section of the IDOC XML generated.'
rgds -
My Bluetooth USB wireless transmitter for my portable BT speakers has quit working. Preferences says, "The selected device has no output controls", it used to work just fine. The internal and a pair of wired external speakers work fine. Can anybody help?
Just tested something and it worked.
If I put the headphones all the way in, the mac recognizes it as a digital output.
But if i don't put it all the way in, it recognizes it as headphones and works perfectly.
It's probably this crappy headphones.
If anyone has the same problem, try this out. -
VOFM formula on output control based on item category(PSTYV)
Hi Gurus,
I created an Output Control requirement in VOFM.
In the requirement ABAP codes, may I know how can I access the list of item lines category (looking for vbap-pstyv in particular) while I am creating the sales order in VA01, because the sales order is not saved yet, so I cannot get from table VBAP ?
Any way to find the variables available ?
Thanks in advance.
Best Regards,
Vasumathi
Edited by: komma vasumathi on Jun 22, 2009 3:26 PMHi there,
When the sales order is created, all data is stored in the internal tables 1st in USEREXIT_SAVE_DOCUMENT_PREPARE, MV45AV0V_VBAP-PSTYV_VALUES
in MV45AFZZ.
So you can refer the fields from there. Item catg is stored in XVBAP table.
But 1 doubt. Why do you want to trigger the O/p before the order is saved? Usually any O/p is triggered after saving the doc.
Once the document is saved, data is stored in data base tables & you can refer from them.
Regards,
Sivanand -
Hello,
I need info abt billing Outputs - The language is maintained in Bill to party (Customer master), Its maintained in Condition record, It can be changed while creating the invoice.
Now my question is, which of the above three cases has got highest priority.
Could some one provide me some info on this?
Regards,
KrishnaBy default, we will maintain language in Bill-to-Party & also Condition record. But if required, it can be chaged at Invoicing level while taking output. Priority will be Bill-to-party, followed by Condition Record.
Regards,
Rajesh Banka -
Hi,
I am trying to create an ORDERS05 IDoc when a PO is created and sent to a folder via EDI processing.
Here are the steps I followed...
1. Created RFC Destination for EDI Subsystem (TCP/IP connection)
2. Created File port and included the RFC Destination in the Outbound trigger tab.
3. Created partner profile (Vendor)
a. Outbound parameters - message type ORDERS,
i. Outbound Options - receiver port - file port created in step 2
basic type - ORDERS05
ii. Message Control - Application - EF
Message Type - NEU
Process Code - ME10
4. Create PO (ME21)
when I look under Menu Header -> Messages it goes to a printer instead of the File Port I created.
Am I missing a step? Please let me know.
Thanks,
SnehaThanks Kalpanashri,
I followed what you said and this is what I received...
<i>Maintain outgoing EDI-connection data for partner 1002514
Message no. VN032
Diagnosis
The system could not locate the EDI partner agreements (outbound) for partner 1002514.
System response
You cannot use transmission medium 'EDI' with this partner.
Procedure
Maintain the EDI partner agreements for partner 1002514. Make sure to create entries for output control as well as for outbound parameters.</i>
Maybe you are looking for
-
can anyone help lol?
-
Help
-
Refresjh Portlets and Discoverer Administrator
hi anybody can tell me why my discoverer portlets don't refresh (gauge portlets) if i make some changes in the parameters, (colors, size, etc) my portlets after update don´t change anything. If i publish a workbook i have the same problem with displa
-
How to create empty BSP page and execute it
Hi, Please give me the steps for creating an empty bsp page and executing it using transaction SE80. I have created a package and a BSP application. I need to get a url for this page that points to a document/image. I need help with this urgently and
-
I have program that gives me the following data:User[type=Call Manager User,id=usersname,authenticated=true]I need to pull out just the part that is "usersname" The length of this part is variable, the rest is not. I don't normally program and am not