IDOC WBBDLD Segment 16 not showing up

In BD52 what object should I use so that WBBDLD05 will show segment 16 for taxes?

I guess I was wrong in stating the question. I found that BD52 does not make a segment in an idoc appear. The issue is that I cannot get segment 16 to show up with the tax code. We have tax codes set up in our system but the segment must have been turned off when our consultants set the system up. We were using another POS software package that was not integrated with SAP ECC. Now we want to use the integrated system and we don't know how to get the segment to show up. Any thoughts?

Similar Messages

IDoc output is not showing blank fields before the carriage return

When we produce the Material Master IDoc (MATMAS), we send it to a ascii file, to a file port. That works fine when we execute BD10 to produce the IDoc and the file. But, the 3rd party mapping software wants to see every field, even if blank, in each segment it is fed. So, let's say the E1MARCM segment is 750 chars, when you add up all the field lengths in the structure, but the last 5 fields are blank. SAP does not include those trailing blanks at the end of the segment in the file. It just puts a carriage return. How can we configure it to output the trailing blanks?

Hi Mark Mathison
In IDoc ....if no value is passed in to that field then, the field wonu2019t be populated in Doc....
There is no chance of getting blank field in IDocs...
Ramesh

Idoc all segments not generated

Dear Everyone,
                      I am doing File to Multple IDOC scenario.Multiple Idocs are generated successfully but only one segment fields are coming.I used 5 segments while doing mapping.
E1KNA1M
   E1KNVVM
     E1KNVPM
E1KNB1M
     E1KNB5M.
             only E1KNA1M segment turned into GREEN,remaining 4 segments are still showing as GREY color only.but i mapped some fileds in all those 4 segments with source fields.IDOC also generated without errors.I need to get remaining 4 segments fields also.I couldn't find what the error is.Any help would be appreciated.
Thanks in Advance
Vinay

Hi,
To get generate the fields of a segment and the segment occurence is 0...unbounded
then you need to map the source field based on which the no of target segment has to be occured. if there is no such source field then need to map the constant to the target segment so that fields under that segment will get generated in the target mapping..
Hope this clears your query..
Regards
Rajesh

Assortment List IDoc - WBBDLD03 Taxcode Segment not creating.

Hi All,
What configurations are required to send the Tax code from Assortment List Idoc 16th Segment. Pls. let me know the steps of configuration verification so that it can be send through Assortment List IDOC WBBDLD03 or 6
Regards
Ashok

Hi Milan
Pls. follow these steps.. for Sending the Tax Codes.
NOTE : Steps for Tax Code Flow to POS
Step 1 : MM42 - Basic Data - Check the following
               Tax Class - (With Value)
               Tax Data - (Country - CA, Tax Category - CTXJ Tax Jurisdiction, Tax Classification - 1 Taxable (0-Non Taxable, 1 Taxable Etc)). Taxs Relevant to Article Taxes.
Step 1.1 : MM42 - Basic Data - Check the following
                  Check for the Assortment List Type, Listing of Assortment to Site in Listing Tab, Price of Article.
Step 2 : WB02 - Customer Tab - Billing Sales Area - Tax Classification - (1-Liable for Taxes)
Tax code is pick up from Site - Address (Country, Region Combination of Site master to Assortment List)
Step 3 : VK11 - Condition Type - CTXJ
This Tax Condition should have a Combination records for Tax Codes in the List. (For Country / State / Customer Classification / Article Classification 1. The table should contain the records for 'CA' - (Canada, Region, Tax Class Cust, Tax Class Artic, Valid from, Valid To, Tax Code)
Step 4 : IMG -> Sales and distribution -> Basic Function -> Pricing -> Pricing Control -> Define and Assign Pricing Procedure -> Maintain pricing procedures (V/08)
               V/08 - Pricing - VKP001 - Sales Price Princing Branch will carry the Pricing Condition to Outbound Idoc WBBDLD.
               Solution : Changed the VKP001 Pricing procedure having the standard tax condition MWSI, this one changed to CTXJ which is of Canadian Tax Condition.
Step 5 : IMG -> Logistics General -> Assortment -> Assortment List -> Maintain Profile for Assortment List -> Selection the Assortment Type -> Check the Condition Type Group
Step 6 : IMG -> Sales and distribution -> Pos Interface -> POS Outbound -> Maintain POS Condition Type Group
               This table is by default Maintained with below Condition types
               MWSI - Output Tax
               MWST - Output Tax
               VKAO - Promo SP IS-R
               VKPO - Sales Price
               Add Additional Condition types which need to send to POS including the condition type of Tax.of Canada
               CTXJ - Tax Jurisdiction Code.
               KA02 - Promotional Discounts % 1
               KA04 - Promotional Discount MD 1
Regards
Ashok

Idoc not showing in R/3

Hi,
Iam Currentl running File to Idoc interface. Message is success in moni also and runtime workbecnh also. But when iam checking R/3 using WE19 tcode by giving date its not showing . It showing like no values found. Can anybody tel me what is the reason?

Hi,
Dont seach with IDOC no in R/3. Check in WE02 transaction not WE19
Search by Date only ........then go under your INBOUND IDOC type node in WE02 in ECC. Also Please check the ECC client no you are posting the IDOC.
Please be confirm in SLD your ECC business system client . And search the IDOC in ECC in same client no.
You can also chek in ID check Adapter Specific Message attributes for ECC business system & also click the Compare with SLD Option.
You can found this option after opening Business system in ID from menu.

Idoc segment not apperaing for PO creation.

Dear All.
Sceanrio:
Once PO is created , NEU ouptut gets triggered.On release of PO, it generates an outbound idoc.
Issue.
In this outbound idoc the segment E1EDKA1 WE is missing.This segment gives the Ship to address in the PO, ie normally the plant address to which the material is shipped.
Analysis:
This PO has 3 line items and these are created by reffering 3 different PR s.So my question here is , whether is this standarad SAP behaviour where Ship to address segment wont get populated into idocs for multiple line item POs.Why i am asking this is that, if suppose the PO has 10 different line items , with 10 different plants.Each plant has different address.Then how system will decide which ship to address will populate in E1EDKA1 WE segment.
Or is there any other behaviours, when the PO has multiple line items.
Please let me know your thoughts on this.
Regards
Shyam

Hello Shyam ,
The reason for this behavior could be that tthe items in the IDOC have a different delivery address maintained in the Ourchase Order. If the delivery address for all items is the same , the segment E1EDPA1 with qualifier WE will be not populated. Instead of generating E1EDPA1 , the system will create one E1EDKA1 segment with qualifier WE. This will prevent on receiving side the creation of the same delivery address for all items.
I hope this information has been helpful.
Best Regards,
Frank Farinella

KFF icon not showing,instead showing segments individually on OAF page

Hi All,
The below problem is regarding KFF.
KFF icon is not showing,instead each individual segments are seen on my details page.
Our client requires to see KFF icon so that when the client click the KFF icon, the page should show the segments assigned to the KFF.
Please help.
Regards

Hi,
What do you mean by KFF icon???
On Oracle forms there is a DFF icon available...[].
And also it is the Standard OAF behaviour that segments are displayed as seperate text inputs or lov Inputs.
I guess there is no symbol for KFF????
Thanks,
Gaurav

Segment builder,not showing results.

hi experts
While creating a campaign i assigned marketing attributes to business partner .its visible in the marketing tab page in the respective bp but in the segment builder its not showing results.

Hello,
have you added the marketing attributes as a data source to the Segment Builder using Transaciton Code CRMD_MKTDS?
Regards
Gregor

Metadata values not showing in Site Studio layout using Idoc Script

Hi All,
We have a SS layout (secondary) with replaceable regions for showing content that is listed in a primary page dynamic list.
Part of the layout shows contribution elements of Contributor Data File content items, but part of layout also shows metadata values. We use  to show the content item Title with no problems.
However, for some content items, some metadata values are not showing on the layout - specifically a custom metadata field called xFinishDate (which is of type 'Date' in Config Man). The code  simply does not work (nothing is displayed) for some content items, despite definitely having a set FinishDate value. Some other content items show this value fine.
The  value works for ALL items, but the  does not, and there appears to be no difference between the items that it does, and does not work for. They are all CDF, same DocType, same CheckIn profile, etc.
The non-working items are all released and indexed. Their Content Information in Content Server shows complete metadata. I have resubmitted the non-working items for reconversion in Repo Man but no luck.
Is there something I am missing? Any help is greatly appreciated.
Luke.

Actually the default DOC_INFO resultset that is on the page seems to be for the content item being loaded into the secondary layout's replaceable regions. This is why DOC_INFO.dDocTitle gives the results expected.
However, I think I have discovered why the xFinishDate value was not showing. Using sapan's code (and modifying it a bit) I was able to print out all the metadata field names and values for default DOC_INFO resultset.
Using this URL as an example: http://www.bond.edu.au/about-bond/jobs-at-bond/BD3_011217
At the top of page region (replaceable) where the Contributor Data File is loaded into, the DOC_INFO resultset is relevant to the content item that is being loaded into the layout (content ID: BD3_011217 - as per the URL format), which is what we want.
However, throughout the Contributor Data File content, if a link is made using the Site Studio link wizard via FCK Editor (in the above case, it is the position description link, which is a link to a PDF) and the link is 'Link to a file' and the 'Choose Target section' is selected as 'Use default website section metadata', the resulting link looks like "http://www.bond.edu.au/about-bond/jobs-at-bond/BD3_011216". Any references to the DOC_INFO resultset on the page after the instance of this link now use the metadata of the content item referred to in the link, not the original content item. I have dumped out the DOC_INFO fields/values in different parts of the layout to prove this. The linked content item has no xFinishDate value so this is why nothing displays (displaying xFinishDate needs to happen after the link to the position description).
I guess I need to either:
- change the way the link is made to the content item to "Link to the Content Item's URL", but I would prefer not to expose the resulting path e.g. "[!--$HttpRelativeWebRoot--]groups/group-name/@account-name/documents/content-type/content-id.pdf"
- explicitly make a resultset using  with the content ID I know I want and use it instead of the default DOC_INFO one. Is there any other way to make a resultset comprising of a single item's metadata?
9.45 SS_GET_SEARCH_RESULTS
■ Description: This is a wrapper around the regular CS GET_SEARCH_RESULTS
service. It allows some Site Studio features to be specified simply as flags and have
the real query syntax be constructed on the server. It can modify the standard
'SearchResults' resultset to contain an additional column called 'ssUrl' which will
contain the Site Studio-friendly url for all of the search results.
■ Parameters:
– siteId: the unique identifier of the site (required).
– ssLimitScope: True/False, restricting scope to within the site only (optional).
– ssUserSearchText: user-supplied search text (optional).
– ssWebsiteObjectType: object type (optional).
– computeFriendlyUrls: True/False, modify results to include ssUrl (optional).
■ Returns: resultset named ’Search Results’.
■ Security: The user must have at write access to at least one security group on the
content server
Thanks to everyone for their help. Almost there!
Edited by: lukeb2112 on 18/01/2010 17:30

Modified idoc values are not reflecting in the IDOC display (ie we02)

Hello Team
I wrote one inbound interface for posting GR by using the IDOC MBGMCR03. In the inbound FM, i wrote some code for retrieving some data and mapping to its relevant fields of the segments. It is working fine but when i see the idoc values in WE02/WE05, i am not able to see the values which i have added in the FM. so please suggest me how to get the values in the IDOC display.
Regds
Raj

Hello Team
Thanks for your replies. Let me put my question in this way to you.
In the inbound FM (ie idoc_input_mbgmcr), i have fetched some values from SAP by using the values which came from PI to that IDOC through mapping. what ever the values i have fetched from SAP in inbound FM, i have mapped them to the relevent segments and finally the complete structure i have passed to BAPI, where it will post GR. All these things are working fine, idoc is also getting successfull.
But when i go and see the successfull idoc values, it is not showing the values which i have mapped in inbound FM. Now i want those values in that Final idoc.
So pls check and suggest.
Regards
Rj

IDOC BOMMAT Is Not Received In Target System

Dear Expert,
I have one problem about ALE. I have distribution model between my system and partner system in other region. This distribution model is set up in my system to receive BOMMAT, MATMAS, BOMORD, DOCMAS, ECMMAS, and SERDAT. From my side, only sending the Audit(ALEAUD).
Previosly the ALE link is was working properly.
Now the problem that I have is, when my partner send set of IDOCs(BOMMAT, MATMAS, BOMORD, DOCMAS, ECMMAS, and SERDAT), my system received all messages except BOMMAT.
I have been trying to search all possibilities in my system, which I can not find any solution for this.
I can say it is not about authorization check since the authorization trace did not show any error.
Thank you very much.

Hello,
SM58 from both system sender and receiver are empty and also all message types had been maintained properly in WE20.
Thanks.

New tables & indexes created do not show up in dba_segments view

Dear all,
I have created 3 tables and some indexes, but these objects do not show up in dba_segments view. Is this a normal behaviour? Previously, with dictionary managed tablespace, I can specify the minimum extent to create, when the table/index is created. But I'm not sure how the locally managed tablespace work. Please do advice. Thank you very much in advance.
I'm using Oracle 11g R2 (11.2.0.1.0) for Microsoft Windows (x64), running on Windows 7.
For the purpose of reproducing this issue, I have created the tablespaces as follow:
CREATE TABLESPACE CUST_DATA
DATAFILE 'd:\app\asus\oradata\orcl11gr2\CUST_DATA01.DBF' SIZE 512K
AUTOEXTEND ON NEXT 256K MAXSIZE 2000K
EXTENT MANAGEMENT LOCAL UNIFORM SIZE 256K
SEGMENT SPACE MANAGEMENT AUTO;
CREATE TABLESPACE CUST_INDX
DATAFILE 'd:\app\asus\oradata\orcl11gr2\CUST_INDX.DBF' SIZE 256K
AUTOEXTEND ON NEXT 128K MAXSIZE 2000K
EXTENT MANAGEMENT LOCAL UNIFORM SIZE 128K
SEGMENT SPACE MANAGEMENT AUTO;
CREATE TABLE CUSTOMER_MASTER (CUST_ID VARCHAR2 (10),
CUST_NAME VARCHAR2 (30),
EMAIL VARCHAR2 (30),
DOB DATE,
ADD_TYPE CHAR (2) CONSTRAINT CK_ADD_TYPE CHECK (ADD_TYPE IN ('B1','B2','H1','H2')),
CRE_USER VARCHAR2 (5) DEFAULT USER,
CRE_TIME TIMESTAMP (3) DEFAULT SYSTIMESTAMP,
MOD_USER VARCHAR2 (5),
MOD_TIME TIMESTAMP (3),
CONSTRAINT PK_CUSTOMER_MASTER PRIMARY KEY (CUST_ID) USING INDEX TABLESPACE CUST_INDX)
TABLESPACE CUST_DATA;
SQL> SELECT TABLE_NAME, TABLESPACE_NAME
2 FROM USER_TABLES
3 WHERE TABLE_NAME LIKE 'CUST%';
TABLE_NAME TABLESPACE_NAME
CUSTOMER_MASTER CUST_DATA
SQL> SELECT INDEX_NAME, TABLESPACE_NAME
2 FROM USER_INDEXES
3 WHERE TABLE_NAME LIKE '%CUST%';
INDEX_NAME TABLESPACE_NAME
PK_CUSTOMER_MASTER CUST_INDX
SQL> SELECT SEGMENT_NAME, SEGMENT_TYPE, TABLESPACE_NAME, BYTES
2 FROM USER_SEGMENTS;
no rows selected

Prior to 11g, when you created a table or whatever, you automatically allocated one extent.
This is now no longer true and depends on a parameter I don't remember.
dba_segments is a summary of dba_extents.
Obviously, if there is no extent allocated, the table (view is defined with inner join) will not show up.
You could qualify this is as a bug and submit a SR to Oracle. But then the performance impact may be huge.
Sybrand Bakker
Senior Oracle DBA

E1EDKT1/E1EDKT2 Segment not displayed in EDIDC

Hello,
We are unable to get PO text in created IDOC , While creation of PO system generated Outbound idoc, but system was not transferred the PO text,
when we cross checked
E1EDKT1
E1EDKT2
These segments not displayed in EDIDC, Check below screen i,e the PO text not transferred through IDOC
Thanks
sapman man

Hi,
We have Created PO and Entered Header text (In Header of the PO) and, Material Text copied from Material master to PO Item level texts.( See Below screen shots
After Save of PO , system Generated IDOC without these texts, How to get these texts in Idoc,
As we know these (E1EDKT1, E1EDKT2) segments not available in EDIDC, as per screen shot. i,e the reason these text not Transferred through Outbound Idoc.
PO Text are not possible to transfer through Idoc, How to transfer these Texts through idoc.
Thanks
sapman man

View log not showing physical SQL generated in OBIEE 11.1.1.6.7

Hi,
I am currently using OBIEE 11.1.1.6.7 version. In this version I am unable to view the physical SQL generated by OBIEE under Administration --> Manage Marketing Jobs --> Select a Job --> Click on View SQL OR Administration --> Manage Sessions--> Select a Job --> Click on View SQL. It is not showing the physical SQL generated by OBIEE for a report or segment which I have executed.
It was available in previous version i.e. OBIEE 10.1.3.4.2.
I have searched in metalink and it has been suggested to use the following <Filters> section into instanceconfig.xml file. I have added the following details into existing instanceconfig.xml file and then restarted the BI services. Still the problem persist.
<Filters>
<FilterRecord writerClassGroup="Console" path="saw" information="16" warning="31" error="31" trace="32" incident_error="1"/>
<FilterRecord writerClassGroup="File" path="saw" information="16" warning="31" error="31" trace="32" incident_error="1"/>
<FilterRecord writerClassGroup="Marketing" path="saw.mktgsqlsubsystem.joblog" information="16" warning="31" error="31" trace="32" incident_error="1"/>
<FilterRecord writerClassGroup="File" path="saw.httpserver.request" information="16" warning="31" error="31" trace="32" incident_error="1"/>
<FilterRecord writerClassGroup="File" path="saw.httpserver.response" information="16" warning="31" error="31" trace="32" incident_error="1"/>
</Filters>
Thanks,
Prasanta

Hi,
Thanks for the reply.
We used to view the log details (physical SQL) using Manage Marketing Jobs in OBIEE10g.
In OBIEE11g we can see the job details and when selecting a job (under Action column Details link) there is an option in left pane as 'View Log'. If I click on 'View Log' it is showing as 'No Logs Found'.
Just wanted to confirm if this is an issue in OBIEE11g.
Also, I believe there is a limitation in 'Manage Session' to view the number of job details whereas in 'Manage Marketing Jobs' section we can increase the number of jobs to be displayed.
Thanks,
Prasanta

IDoc type could not be determined for the IDoc in F110

Dear All,
The below mentioned error is encountered by us in F110.We have check all the setiing and not able to find the solution for this error.
Now our heads has gone for a toss....can anyone kindly suggest what and where we have missed out.
The system is not creating the IDOC file.....
IDoc type could not be determined for the IDoc
Message no. B1090
Diagnosis
The IDoc passed to the ALE layer could not be processed. The specifications passed in the control record were not correct.
The basic IDoc type (field EDIDC-IDOCTP on the outbound side or EDI_DC-IDOCTYP on the inbound side)has not been specified for this IDoc.
The attempt to read the basic IDoc type from table EDIDO also failed. No table entry was found for IDoc type from field DOCTYP.
Procedure
Possible error sources:
- The calling program did not provide values for the fields specified above correctly. Make a note of the transaction in which this error occurred and consult your ALE administrator.
- The IDoc type is not known in your system and must be maintained.
Kindly do the needful.
Regards

If you want to create IDocs from the proposal run, outbound parameters (we20) with the 'Test' flag are required in addition.
see OSS note 504230 : Message EUPEXR forms the logical unit around the individual payment messages (PAYEXT IDocs). The E1IDRD1 segments contain the IDoc numbers of the payment messages in field DOCNUM. Segment E1IDRS1 contains check sums (total of all amounts, account numbers, bank numbers, number of payment messages). This information is provided for the EDI subsystem. Set up EUPEXR In Transaction WE20 for the partner profile for the house bank, create the outbound parameters for message type EUPEXR with IDoc type IDCREF01. If you want to create IDocs from the proposal run, outbound parameters with the 'Test' flag are required in addition.

IDOC WBBDLD Segment 16 not showing up

Similar Messages

Maybe you are looking for