Output type works different when VF01 and VF02 ,why?

For Invoices related to a B2B order the output type ZB01 does not always come up during invoice creation time. If we go into the invoice via VF02 it will pop up immediate. But invoices are created by batch jobs and then not 100% of the ZB01 get created. Partners are complaining and need this to be 100% working.
what's the probable problem with it?

Atish
I Searched 'VF02' already ,but there is no user exit to handle with it .
Maybe because it's B2B ,we can't find it in our SAP system ..
What's the next step should I do

Similar Messages

Out type for B2B invoice works different via VF01 and VF02

For Invoices related to a B2B order the output type ZB01 does not always come up during invoice creation time. If we go into the invoice via VF02 it will pop up immediate. But invoices are created by batch jobs and then not 100% of the ZB01 get created. Partners are complaining and need this to be 100% working.
what's the probable problem with it?
Appreciate your help ,Thanks in advance

Atish
I Searched 'VF02' already ,but there is no user exit to handle with it .
Maybe because it's B2B ,we can't find it in our SAP system ..
What's the next step should I do

Billing Output Access Sequence behaving differently in VF01 Vs VF02

Hi All,
Scenario: For RD00 output from G2 Credit memos there is a customised access sequence. At the top as a first sequence a new table was added with fields as Sales Org/Billing Types/ Billed-to/ Order Reason. All the required changes to add 'order reason' in field catalogue and in output structures are done with development. System allows to maintain required output master record in VV31 as required.
Issue: Upon creating a credit memo the output access sequence ignores the newly added first table at the top (most specific) and jumps to the second one and output gets determined with second access although it should have considered the first one first. (Exclusive indicator marked for each step in Acc Seq) This is the case when the credit memo is seen in VF03 upon creation. But if the same document is opened in change mode VF02 it corrects the output and as required the first access gets determined.
Please advise what could be different in VF01 Vs VF02 as the first leads to wrong output and the later determines the right one, keeping all settings same.
Thanks,
Hemant

This is a bit of a long shot, but hereu2019s an idea.
The problem may be that your order reason gets populated by a user exit in the billing document creation process, and this user exit has not yet executed when the output determination kicks off.
Put a break point in the user exit. If an output from the second key combination is already determined when the break point is reached, then the source of the problem is confirmed.
Regards,
Ken

VF01 and VF02

Hi all,
I have defined same output type for VF01 and VF02 and with same parameters. My user settings are set to my default printer PRINT. However when i do an issue output to, it picks up PRINT when done thru vf02 but picks up LOCL when done thru vf01.
Can you please guide how to ensure the entries in NAST table has same printer as the one in user default setting ?
thanks,

Hi,
Confirm with your SD consultant first what are all the settings that he has done for printing the forms.
Even your Basis guy can make the printer settings default as PRINT so that when ever output device is triggered then the settings done by basis guy will call.
Cheers!!
Balu

TableView LINEEDIT works differently when viewed through Portal

I have a simple table with a few columns of data that I display and allow the user to change a row using the selectionMode = "lineedit". The columns are all controlled using htmlb tableViewColumns.
When I test my application from the WebAs the table looks fine. If a user selects a row they can see the entire amount of text that appears in a column they want to change
However, when the BSP comes up in our SAP portal and the user selects a row only the first 20 (or so) characters can be seen and the user must use the arrows keys to get to the part of the text they wish to change. Is this a setting somewhere?

For the <htmlb:inputField> look at attributes maxlength, size and width.
<b>width:</b> Determines the text width for the input field. We recommend that you use the size attribute instead of width.
<b>size:</b> Determines the size of the input field.
<b>maxLength:</b> Maximum length of the user input.
I must admit that this documentation is not tell me enough. Will ask on Monday about this.
As for your remark "works differently when viewed through Portal": You keep in mind that once a BSP application is running with the portal, all stylesheets (*.CSS) files are loaded from the portal server, and not the webAS.
Now it could happen that you are running an EP and an older (or incompatible) patch level than your BSP stylesheets are at the moment. For EP6, starting from what I remember at SP11, there is planned a technique to install the latest stylesheets from service market place. You ask about this via OSS, queue EP-PIN-?-STY (something like this).

I get a message that itunes has stopped working. When I check out why it is because of the dep security on my computer. When I try to find the program for itunes for the .exe file i cannot find it to turn off the dep for that file

I get a message that itunes has stopped working. When I check out why it is because of the dep security on my computer. When I try to find the program for itunes for the .exe file i cannot find it to turn off the dep for that file

I found the file but when I added it to the list for the Data Execution Program to ignore , I received a message that the Program.x86/itunes file must have the DEP on in order to run. Anyone else having this problem ?

Output types are different in VF02 than in VF03 (A particular output type Z*** does not appear in VF03)

Hi Experts,
When I check the billing document (Go to>Header>Output) there are 3 output types. After executing VF02, an output type is added (EDI). Why does this particular output type (Z***) not appear in VF03?
- What are the related configurations for this?
- Is this a possible ABAP issue? To my knowledge, custom programs usually do not result to this kind of behavior.
Thanks in advanced,
Jack

Jack Rockefeller wrote:
I'm not a functional consultant but an ABAP consultant.
Ah, OK, that explains it. Jack, I'm sorry but it's not quite feasible to explain the whole output determination configuraton in a discussion post. Here is a wiki page if you have some time for reading. It's not very thorough but you could google for more. But it would be more efficient to just ask an SD consultant.
Also in VF02 look at the Output Determination analysis (it's somewhere in the menu in the Output screen) and see if it makes any sense to you.

Key Figure data type/length differs in BI and source system

Hi all.
It is a strange question, but we need an explanation to our "strange" client. Why many fields which are DEC 13 in source system became CURR 09 in BI? DEC->CURR type switch seems reasonable, but not the length. I guess the shorter numeric field is the less precise it can keep...
Does SAP give any explanation for that?

Hi,
     If you are expecting the data to be aggregated in the cube and if the data is loaded by different requests, then in that case the data wouldnot be aggregated.
EX: CHAR1   CHAR2    CHAR3   CHAR4     CHAR5    CHAR6    CHAR7    KF1   KF2   KF3
         A               B              C            D        E              F             G          10     20    30
          A               B              C            D        E              F             G          10     20    30
sUPPOSE IF THE ABOVE 2 ROWS OF DATA ARE GETTING LOADED IN THE SAME REQUEST, then you can expect the data to be aggregated and the o/p of the KFs will be 20, 40 and 60 respectively.
In case the loading is done with separate requests, then your data will not be aggregated.
This is becuse in the cube, Request ID (under the Data Package Dimension)    is one of the dimension and this differs when the requests are different.
Regards
Sunil

Purchase order - output type vendor different from PO vendor

Hello,
we have created a new output type that sends our purchase order as emails. The email will be sent to the vendor email address that is entered together with the output type under messages of a purchase order.
We need the emails to be sent an internal email address, so we don't send them to the vendor right away. For that reason, we have created a new vendor X that has our email address, only for that purpose.
If we now have a purchase order with vendor Y (this is the real vendor) and use our new output type along with vendor X (this is the vendor only created for sending the PO as email to us), will this affect the accounting process of how the purchase order is handled? Or does vendor X have no impact on accounting in this case?
Thanks
Anne

Hi Anne,
Vendor available (in your eg. X) in the output type messages screen for PO does not have any impact on accounting processes of main vendor (in your eg Y).
-Ravi

Group GL V/s GL Report is working differently in Production and Development

Dear Experts,
I have created one Report which displays Group GLs and its Cumulatve Balances. The Format is is as below :
Items                   Balances
1001                     XXX
1002                     XXX
1003                     XXX
1100                     XXX
With Report Report Interface and Go to option I have connected the above with another Report
If you right click on any of the Item say "1002", It will show its drill down Report that is Group Gl Wise GL, as below
Output 1
Items       GL A/c Balances
1002                     XXX
                10021   XXX
                10022   XXX
If you Right Click on the Heading "Item", It show display all Items with its GL Account like
Output 2
Items       GL A/c Balances
1001                     XXX
10011   XXX
10012   XXX
10013   XXX
1002                     XXX
10021   XXX
10022   XXX
1003        10031   XXX
10332   XXX
10033   XXX
The Above output 1 and Output 2 works in Development, but in Production only Output 1 (i.e. Selected one Items with its GL Account) works, Output 2 (i.e. all Items with its GL Account) does not work in Production System.
Kindly let me know whatt could be the reason and its resolution ????
Regards
Ritesh   M
Edited by: Ritesh M on Jan 6, 2010 6:40 AM

Check two things in the production system:
1) Is the mapping between G/L group and G/L accounts correctly maintained?
2) Are there real postings on all the accounts which you have listed?

HT2946 Why is the contrast of my images totally different when processed and then opened in CS4? Does anybody else have this issue?

Why does the contrast in my images processed in Aperture look markedly different when opened in CS4? The images look fab on the screen in Aperture - even if these are then opened in CS4 from Aperture they look different - much flatter. This is a new issue. I am a wedding photographer and an album processed in Aperture has been sent back by my wedding album printer saying the images all lack contrast! Can anybody shed any light on this! I have checked colour spacing etc!

I Also have this problem!!
In my situation, the screen simply started exhibiting the same symptoms a few weeks ago (early February) for no apparent reason. At first I thought the screen was dead, but discovered the heat solution by accident. Now I turn it on and keep it from going to sleep until I go to bed. Thank goodness the battery is still awesome on this thing.
I bought it new and still has the original screen, I keep it at home (never below 62 degrees). Coincidentally, this happened a day or two after the expiration of the warranty!! Any help figuring this one out would be eternally appreciated.
iPad mini retina Wi-Fi, iOS 8.1.3

Mdx queries work different on 2008R2 and 2012

Hi all,
we have migrated our SSAS database from 2008R2 to 2012 recently. And I found strange thing. The mdx query below (generated by Cognos) worked quite fine on 2008R2
WITH
MEMBER [Territory].[Territories].[XQE_MDF_CM0] AS IIF(COUNT(INTERSECT(DESCENDANTS([Product].[Products].CURRENTMEMBER, [Product].[Products].[Product]), XQE_NS0) AS [XQE_SA0] , IncludeEmpty) > 0, AGGREGATE([XQE_SA0], ([Territory].[Territories].DEFAULTMEMBER)),
NULL)
SET XQE_NS0 AS FILTER([Product].[Products].[Product].MEMBERS, [Product].[Products].CURRENTMEMBER.PROPERTIES("MEMBER_KEY") = "713077" OR [Product].[Products].CURRENTMEMBER.PROPERTIES("MEMBER_KEY") = "857127" OR
[Product].[Products].CURRENTMEMBER.PROPERTIES("MEMBER_KEY") = "857128" OR [Product].[Products].CURRENTMEMBER.PROPERTIES("MEMBER_KEY") = "713080" OR [Product].[Products].CURRENTMEMBER.PROPERTIES("MEMBER_KEY")
= "717113" OR [Product].[Products].CURRENTMEMBER.PROPERTIES("MEMBER_KEY") = "856597" OR [Product].[Products].CURRENTMEMBER.PROPERTIES("MEMBER_KEY") = "857129" OR [Product].[Products].CURRENTMEMBER.PROPERTIES("MEMBER_KEY")
= "713083")
SELECT
CROSSJOIN({[Date].[Time].[Month].&[201409]}, CROSSJOIN(HIERARCHIZE(GENERATE(XQE_NS0, ANCESTORS([Product].[Products].CURRENTMEMBER, [Product].[Products].[Brand]))), {[Measures].[QTD Sales Revenue]})) DIMENSION PROPERTIES PARENT_UNIQUE_NAME, PARENT_LEVEL
ON AXIS(0)
FROM [Nemesis]
WHERE ([Territory].[Territories].[XQE_MDF_CM0]) CELL PROPERTIES VALUE, CELL_ORDINAL, LANGUAGE, FORMAT_STRING
But on 2012 version there was an interesting thing
Result from (2008R2)
2014/09 2014/09
GALVUS GALVUSMET
QTD Sales Revenue QTD Sales Revenue
2346360.3062295 5550927.34167495
Result from (2012)
2014/09 2014/09
GALVUS GALVUSMET
QTD Sales Revenue QTD Sales Revenue
5550927.34167495 5550927.34167495
both results have been duplicated. Finding out a reason it looks like the where Clause which should filter products across first calc member works wrong. So when comment out where clause outcome looks right (I put all products from both brands by the way).
But clients have to choose products to filter.
I am just wondering if anyone encountered a similar issue, or
even if somebody have the solution.
Many thanks,
Denis.
Denis

In other words filter by set in WHERE clause is not working via calc member and aggregate function.
Any ideas guys?
Denis

Output type configured as "CanNotChanged" (NACE) and process mode 2 in VF31

When we configure a billing document output type as "CanNotChanged"
(NACE), we can no longer use the processing mode 2 in the VF31
transaction to repeat the printing of the documents which have been
printed allready once.

Acording to SAP, this is the standard behaviour of the software

How different when i5 and i7 work with Final Cut Studio?

27-inch models only, one of the following:
2.66GHz quad-core Intel Core i5 processor with 8MB shared L3 cache; Turbo Boost dynamic performance up to 3.2GHz
2.8GHz quad-core Intel Core i7 processor with 8MB shared L3 cache; Turbo Boost dynamic performance up to 3.46GHz; Hyper-Threading for up to eight virtual cores
May I get the "up to 2.3x faster performance with Final Cut Studio" with i5?
Thanks advanced.

It looks very convincing to pay more for i7. Thanks a lot.
I agree, and also get 8G or more of RAM like Switch900 suggests. You can save money on that by buying it from a third-party vendor.
Check out the new remodeled MacOSG website! 24-hour Apple-related news & support.
 MacOSG: An Apple User Group  iTunes: MacOSG Podcast  Follow us on Twitter: MacOSG

XMLTYPE.transform works differently in SQL and PL/SL

Hi, when I use XMLTYPE.transform in SQL, it's working fine - try this:
SELECT XMLTYPE.createXml('<data/>').transform(XMLTYPE.createXml('<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:output method="html" version="1.0" encoding="UTF-8" omit-xml-declaration="yes" indent="yes" />
<xsl:template match="/">
<HTML>
<BODY>
<TABLE>
<TR><TD><INPUT readOnly="readOnly" size="19" maxLength="30" type="text" value="test..."/></TD></TR>
</TABLE>
</BODY>
</HTML>
</xsl:template>
</xsl:stylesheet>')).getClobVal() FROM DUAL;
But when i tried to do tha same in PL/SQL, i obtain error - try this:
DECLARE
lClob CLOB;
lXsl XMLTYPE;
lXml XMLTYPE;
BEGIN
lXml := XMLTYPE.createXml('<data/>');
lXsl := XMLTYPE.createXml('<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:output method="html" version="1.0" encoding="UTF-8" omit-xml-declaration="yes" indent="yes" />
<xsl:template match="/">
<HTML>
<BODY>
<TABLE>
<TR><TD><INPUT readOnly="readOnly" size="19" maxLength="30" type="text" value="test..."/></TD></TR>
</TABLE>
</BODY>
</HTML>
</xsl:template>
</xsl:stylesheet>');
lClob := lXml.transform(lXsl).getClobVal();
END;
Error is:
ORA-31011: XML parsing failed
ORA-19202: Error occurred in XML processing
LPX-00210: expected '=' instead of '>'
Error at line 7
ORA-06512: at "SYS.XMLTYPE", line 138
ORA-06512: at line 20
Oracle version is 11.2.0.2.0.
Knows anybody where is the problem?
Thanks, R. Kazimir

Hi,
Actually it does not work for both.
Remove .getClobVal() method and see what happens :
SQL> SELECT XMLTYPE.createXml('<data/>')
2 .transform(XMLTYPE.createXml('<?xml version="1.0" encoding="UTF-8"?>
3 <xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
4 <xsl:output method="html" />
5 <xsl:template match="/">
6 <HTML>
7 <BODY>
8 <TABLE>
9 <TR><TD><INPUT readOnly="readOnly" size="19" maxLength="30" type="text" value="test..."/></TD><
/TR>
10 </TABLE>
11 </BODY>
12 </HTML>
13 </xsl:template>
14 </xsl:stylesheet>'))
15 FROM dual;
ERROR:
ORA-31011: Echec d'analyse XML
ORA-19202: Une erreur s'est produite lors du traitement la fonction XML (
LPX-00210: '=' attendu plutôt que '>'
Error at line 1
)Besides, using getClobVal() in the SQL version produces an invalid output :
<HTML>
<BODY>
<TABLE>
   <TR>
    <TD>
     <INPUT readOnly>
     </INPUT>
    </TD>
   </TR>
</TABLE>
</BODY>
</HTML>The readOnly attribute is not well-formed.
Even stranger : change the just the case of the attribute value, e.g. "readOnly" to "readonly", and it works!
I'm not sure what's happening here. Most likely a combination of bugs regarding html output method.
As a workaround, you can use output method "xml" instead. Works in any cases.
On a side note, in your version, getter methods like getClobVal() are deprecated. Oracle now recommends using XMLSerialize function.
The same goes with XSL transformation, where one should use XMLTransform instead of transform() method.

Output type works different when VF01 and VF02 ,why?

Similar Messages

Maybe you are looking for