Posting log for source flow type/update type

we have run fix and post derived business transaction in last friday for transaction ID: 3309, this is FX transaction, and it is posted, but in the posting log, it only shows update type ZDB_0012 is posted with 2300 USD, how and where is it derived, it doesn't show, so how can I view the source flow type and derivation steps (instead of going to SPRO derivation or position management procedure, I prefered analyze it in front end transaction)
now if we go to posting journal list, we also can't find such info. any way to find out, is this update type ZDB_0012 assigned in position management procedure also? which tab?

Check the BizTalk Administrator Group has the read permissions.
Refer: Cannot open log for source 'BizTalk
ESB Toolkit 2.1'. You may not have write access. ---> System.ComponentModel.Win32Exception: Access is denied
Alternatively, you should also refer the
below post.
Production Installation of the Toolkit
Cannot open log for source ‘BizTalk ESB Toolkit 2.1′
Rachit
Please mark as answer or vote as helpful if my reply does

Similar Messages

Flow with update type SE3003 from 04.09.2014 was only fixed

Hi Experts,
I Have a warning message in TBB1 here.
I want to post to GL!
Thanks for any help with this.
Flow with update type SE3003 from 04.09.2014 was only fixed
Message no. TPM_TRAC1213
Effects on Customizing
You can define when this system message is to be issued in accordance with your requirements.
You do this in Customizing as follows: Cross-Application Components -> Bank Directory -> Change Message Control.
The application area and message number can be taken from the technical documentation.

Hi Jyoti Mohta
My screenshot is in Vietnamese!
I customized SE3003 as Bond Discount. Here is my TBB1 screenshot.

53A comm paper: Flow with update type MM1203- from 05.10.2011 was only fixe

In TBB1 for a transaction of type 53A I get the message: ""Flow with update type MM1203- from 05.10.2011 was only fixed.
What should I do in this case? And with which transaction?
Edited by: EI18 on Feb 24, 2012 9:31 PM

Hi,
is this the 1st time you're posting this UT? If so, have you checked the "Indicate Update Types as posting relevant" customizing? If not, have you implemented SNotes recently? If so, check the OSS and in case there is no corresponding SNote to solve the problem -> create a OSS-message.
Regards
Lorenz

Stk posting change for Material received in movement type 101

Experts,
A material received in Mov type:101 / Inspection type : 01 and rejected during Inspection was posted in To Reserves instead of Return Delivery.
How to change the posting to Return delivery stock from Reserves stock.
Regards,
RPV.

Dear,
First check reservation is created against reserv stock of material.
You can check reservation with MB23.
If yes than delete it first and than create return delivery for material with MIGO.
Regards,
Mahesh Wagh.

Searching for source in unrecognized file types

Using DW CS5, I'm unable to find text while searching that is in some of my files. I think this might be because these files are not recognized as source code by Dreamweaver. They are PHP files but they have the extension .ctp instead (because they are Cake files).
Is there any way to get Dreamweaver to consider these files when searching? I have already specified that Dreamweaver should be used to edit these files in Preferences -> File Types / Editors.
Thanks,
Stephen

Stephen,
Using DW CS5, I'm unable to find text while searching that is in some of my files. I think this might be because these files are not recognized as source code by Dreamweaver. They are PHP files but they have the extension .ctp instead (because they are Cake files).
Is there any way to get Dreamweaver to consider these files when searching? I have already specified that Dreamweaver should be used to edit these files in Preferences -> File Types / Editors.
Yes. This TechNote explains it:
http://kb2.adobe.com/cps/164/tn_16410.html
Randy

Poster frame for cover flow view with safari bookmarks?

i have a friend on a pc who wanted to have his bookmarks display in a visual way so that he doesnt forget about them. so i told him to download safari for windows and use the cover flow view. he likes it, but some sites are not very recognisable by just the thumbnail of the front page. so i was wondering whether there is a way (or a workaround) to choose another image/icon for these bookmarks in the same way that it is possible to select any scene from a movie and have that be the icon/poster frame.
i hope i havent expressed this unclearly. thanks.

Since just moving all my music to a NAS I was here researching the same issue. I can see the other three (only when music is specifically selected) but not Cover Flow. I believe it has been disabled. I played around with grid view with 428 albums and iTunes for Windows loads the art fresh evertime you start it and, on the smallest art size in grid view, it took a bit of time to load all the art.
If Cover Flow needs to cache up all the art work in advance then I could see how it would easily take my setup between 45 seconds to a minute to cache them all up.
Perhaps that would feel too clunky for Apple especially if one were to aggressively swipe through a set that wasn't completely cached.

Security lending no update types found for prod. type 77B, trans.type 100

Hello
In FTR_CREATE for product type 77B Open-Ended Securities lending I get following error:
No update types found for prod. type 77B, trans. type 100, sec.acct cat.
Message no. TRS0835
how do I solve this?
regards
Arjan
Edited by: Arjan Hogenes on Dec 8, 2009 6:51 PM
I have in customizing in "Update types for position update" for product type 77B, transaction type 100:
Product Type    77B   Open-Ended Securities Lending
Transactn Type 100   Loan
Update Type for Open                      SL1990-
Update Type for Close                     SL1992+
Update Type for Underlying / Exercise     OTC003
Edited by: Arjan Hogenes on Dec 8, 2009 6:55 PM
Edited by: Arjan Hogenes on Dec 8, 2009 6:58 PM

Prasad,
I followed your instructions and changed customization for Update type for Position Update type with standard Update types;
OTC001
OTC002
OTC003
but I still get the same error.
In TRM-Trans Mgr-OTC Derivatives-Transaction Mgt-Update Type-Assign FLows type to Update Types
I have:
6 Derivatives     1990     Securities Lending: Basis Flow     - Outflow     SL1990-     Securities Lending: Basis Flow
6 Derivatives     1991     Sec. Lending: Lending Revenue     + Inflow     SL1991+     Securities Lending: Lending Revenue
6 Derivatives     1992     Sec. Lending: Reverse Posting     + Inflow     SL1992+     Securities Lending: Reverse Posting
6 Derivatives     1993     Securities Lending: Agent Fee     - Outflow     SL1993-     Securities Lending: Agent Fee
6 Derivatives     1994     Sec.Lending: Cash Collateral     + Inflow     SL1994+     Securities Lending: Cash Collateral Inflow
6 Derivatives     1994     Sec.Lending: Cash Collateral     - Outflow     SL1994-     Securities Lending: Cash Collateral Outflow
In TRM-Trans Mgr-Listed Derivatives-Transaction Mgt-Flow Type-Assign FLows type to Transaction Type
I have
77B     Open-Ended Securities Lending     100     Loan     1990
77B     Open-Ended Securities Lending     100     Loan     1991
77B     Open-Ended Securities Lending     100     Loan     1992
77B     Open-Ended Securities Lending     100     Loan     1993
77B     Open-Ended Securities Lending     100     Loan     1994
77B     Open-Ended Securities Lending     100     Loan     1995
Any other suggestion for the error "No update types found for prod. type 77B, trans. type 100, sec.acct cat.
Message no. TRS0835"?
many thanks in advance. I Look forward to your answer!
kr
Arjan

Error in Securities DBT update types

Hi experts
We are using securities module (Transaction manager) to manage our stock (equity) transactions.
We have defined the update types for (DBT_E001 and DBT_B001) as not relevant to posting as i do not want to post the gain / loss on sale of securities in some companies (say A) using these DBTs.
However for a few other companies (say B) i have to post the accounting entries. Hence we have made the update type relevant to posting.
But with this it generates accounting entries for co code A as well as B.
I have also tried to make "offline" in control of online calculation of DBT. but it only postpones the flow generation. i have to generate and post the flows before i do key date valuation.
I want to activate DBT flows for co code B but not for A.
Please suggest
Regards
Gaurav Gupta

Hi Gaurav,
Your rqmt can not be addressed by making update types relevant for posting, as update types are not cocd specific. You need to use following specifications seperately for each company code:
a. seperate Accounting Code for each cocd if the valuation class is same for both cocd, else maintain different valuation class.
b. Different Position Management procedure for each Company Code based on few Key fields (Accounting code/Val Class)
c. Assignment of each PMP to respective Acct Code/Valuation Class
d. Then you copy existing update type DBT_E001 and DBT_B001 and make a copy.
e. Mark newly created update type not for posting
f. Assign newly created update type in Dervied Business Transactions of new PMP instead of DBT_E001 and DBT_B001
By setting above, for both cocd the flows generated by system will be same but with different update type and one set of update type is already marked for posting and other not.
Otherthan this, another alternative is to maintain dummy GLs in Acct Determination so that no amount will post to actual GLs based on Cocd.
Hope this will solve your problem.
Regards
Prasad AV

Posting Key for Credit memo need to change

We are haveing cr 1 and dr 50 posting key for Customer invoice,
for credit memot also same. when we create Credit memo it addsup into revenue which is wrong.
WE need to change posting key for Credit memo(G2 doc type)
please provide Tcode /path for it
Thanks in advance,
-Sam

Hi SAM,
1.Tcode: OB41 for configuring posting key
2. IMG --> Sales and Distribution --> Basic Functions --> Account Assignment -> Revenue Account determination -->
Define and Assign Account Keys.
Reward if useful.
Regards
JACK

Change log for material number range

Hi All,
can you guys please tell me how to find the change log for changes done in material type number ranges that is the thru tcode MMNR although its a customization change but as its for number ranges so there is no transport request involved so it is not possilble to see the import of transport request

in transaction MMNR
from menu GOTO > change log
or in transaction SNUM
from menu GOTO > change log

Audit logs for tables

Dear all,
I have a requirement of implementing audit logs for tables to insert,update,delete operations. Is there any way to achieve this since triggers are present only for insert,update and delete ?
I am using database 9.2.0.3.
thanks in advance.

Hi,
After I turn on audit trail on the database sever and issue DML statment. I have found nothing in the audit table.
1) Set "audit_trial" = true in teh init.ora file
2) Run the $ORACLE_HOME/rdbms/admin/cataudit.sql
3) Connect sys/password by sysdba and issue the following command:
- AUDIT SELECT TABLE, UPDATE TABLE, INSERT TABLE, DELETE TABLE BY APPS BY ACCESS;
Do I need to re-set the database after step 1? or I have made some wrong.
Thanks.

Update types relevant for posting - IRR SWAP

Dear Experts,
Wwhen implementing a IRR SWAP, you are normally not supposed to book the reduction in nominal amount (Update Type : DE1105-) and the increase in nominal amount (Update Type: DE1105+).
For a specific requirement this should be on the other hand possible at my client. I tried to activate the mentioned update types as relevenant for posting, but when posting them with TBB1 nothing happens.
Anyone an idea on how to post these update types?
Kr,
Stef

Hi Gregory,
I just figured out. Make Flow Type 1105 as "Relevant to posting" and then check if DE1105 +/- are relevant for posting in "Indicate Update Types as Relevant to Posting". This should resolve your issue too.
Regards,
Abhinav

Update types in infopackage for generic data source

Hi,
Suppose if we create a generic data source,then
1) What are update types availbale in infopackage for tha generic t data source?
2) Is there any link between,the selection on the
i) type delta type select
ii) the field selected i.e like timestamp,cal month,numeric pointer.
3)do we have delaa option at info package level?
I think you understood my doubts.
Regards
Naresh.

hi siva raju,
yes our's is bi 7.0.but there are two DTP with the same optoion of DELTA.It pull the data from ds to info cube.
one more thing,how are the delta records picked from the r/3 to bw?its through Infopackage Am i right?
If possible please tell me the entire flow of data goes for a generic data source.
i.e
how to load data?
how to set delta?
how do we load deltas to bw.?
Regards
Naresh.

Exception Message: TF270015: 'MSBuild.exe' returned an unexpected exit code. Expected '0'; actual '1'. See the build logs for more details. (type UnexpectedExitCodeException)

Hi all,
I have TFS2012 and run several projects.
We encounterwed with such an error while using Build server.
Overall Build Process
Initial Property Values
AgentSettings = Use agent where Name=* and Tags is empty; Max Wait Time: 04:00:00
BinariesSubdirectory =
ConfigurationFolderPath = $/CTI/DEV/DEV_INT/source/TeamBuildTypes/EPhone_DIT
DoNotDownloadBuildType = False
LogFilePerProject = False
MSBuildArguments =
MSBuildPlatform = Auto
RecursionType = OneLevel
SourcesSubdirectory =
TestResultsSubdirectory =
Verbosity = Diagnostic
00:00
Get the Build
00:00
Update Build Number
Initial Property Values
BuildNumberFormat = $(BuildDefinitionName)_$(Date:yyyyMMdd)$(Rev:.r)
Final Property Values
BuildNumberFormat = $(BuildDefinitionName)_$(Date:yyyyMMdd)$(Rev:.r)
Result = Ephone_DIT_Deploy_20150424.1
01:56
Run On Agent (reserved build agent U4VMDWODBDEV03 - Agent1)
Initial Property Values
MaxExecutionTime = 00:00:00
MaxWaitTime = 04:00:00
ReservationSpec = Name=*, Tags=
00:00
Get the Build Directory
Initial Property Values
Result = d:\temp\217\CTI\Ephone_DIT_Deploy
01:53
If Not String.IsNullOrEmpty(ConfigurationFolderPath)
Initial Property Values
Condition = True
01:53
Run TfsBuild for Configuration Folder
Initial Property Values
BinariesSubdirectory =
BuildDirectory = d:\temp\217\CTI\Ephone_DIT_Deploy
CommandLineArguments =
ConfigurationFolderPath = $/CTI/DEV/DEV_INT/source/TeamBuildTypes/EPhone_DIT
DoNotDownloadBuildType = False
LogFilePerProject = False
MaxProcesses = 1
NodeReuse = False
RecursionType = OneLevel
SourcesSubdirectory =
TargetsNotLogged =
TestResultsSubdirectory =
ToolPath =
ToolPlatform = Auto
Verbosity = Diagnostic
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\MSBuild.exe /nologo /noconsolelogger "d:\temp\217\CTI\Ephone_DIT_Deploy\BuildType\TFSBuild.proj" /m:1 /nr:False "@d:\temp\217\CTI\Ephone_DIT_Deploy\BuildType\TfsBuild.rsp"
00:08
Getting sources
00:02
Labeling sources
00:19
Built $/CTI/DEV/DEV_INT/source/TeamBuildTypes/EPhone_DIT/TFSBuild.proj for target(s) CompileConfiguration.
00:19
Built $/CTI/DEV/DEV_INT/source/TeamBuildTypes/EPhone_DIT/TFSBuild.proj for target(s) CompileSolution.
00:19
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.sln for default targets.
00:05
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol/Communications.Protocol.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/CTIException/CTIException.csproj for default targets.
CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor
00:01
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/Common/Common.csproj for default targets.
CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor
CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor
CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/CTIException/CTIException.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/Common/Common.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
00:10
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Softphone/Communications.Softphone.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol/Communications.Protocol.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/CTIException/CTIException.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
00:01
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol.Proxy/Communications.Protocol.Proxy.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol/Communications.Protocol.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol.CTIOS/Communications.Protocol.CTIOS.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol/Communications.Protocol.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/CTIException/CTIException.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Softphone.DelphiCallConn/Communications.Protocol.DelphiCallConn.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol/Communications.Protocol.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor
CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor
00:05
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.DataModel/EPhone.DataModel.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/Common/Common.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
00:02
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/ChannelIntegrator/ChannelIntegrator.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/Common/Common.csproj for default targets.
CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor
CSC: Assembly generation -- Referenced assembly 'System.EnterpriseServices.dll' targets a different processor
CSC: Assembly generation -- Referenced assembly 'System.Web.dll' targets a different processor
CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor
CSC: Assembly generation -- Referenced assembly 'System.EnterpriseServices.dll' targets a different processor
CSC: Assembly generation -- Referenced assembly 'System.Web.dll' targets a different processor
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.Workflow.Interface/EPhone.Workflow.Interface.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Microsoft.Common.targets (1605): There was a mismatch between the processor architecture of the project being built "MSIL" and the processor architecture of the reference "d:\temp\217\CTI\Ephone_DIT_Deploy\Binaries\Debug\EPhone.dll",
"x86". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take
a dependency on references with a processor architecture that matches the targeted processor architecture of your project.
00:02
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Ephone.Workflow/EPhone.Workflow.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.DataModel/EPhone.DataModel.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.Workflow.Interface/EPhone.Workflow.Interface.csproj for default targets.
00:01
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneReporting/EPhoneReporting.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.DataModel/EPhone.DataModel.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.Workflow.Interface/EPhone.Workflow.Interface.csproj for default targets.
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Microsoft.Common.targets (1605): There was a mismatch between the processor architecture of the project being built "MSIL" and the processor architecture of the reference "d:\temp\217\CTI\Ephone_DIT_Deploy\Binaries\Debug\EPhone.DataModel.dll",
"x86". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take
a dependency on references with a processor architecture that matches the targeted processor architecture of your project.
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Microsoft.Common.targets (1605): There was a mismatch between the processor architecture of the project being built "MSIL" and the processor architecture of the reference "d:\temp\217\CTI\Ephone_DIT_Deploy\Binaries\Debug\EPhone.dll",
"x86". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take
a dependency on references with a processor architecture that matches the targeted processor architecture of your project.
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Microsoft.Common.targets (1605): There was a mismatch between the processor architecture of the project being built "MSIL" and the processor architecture of the reference "d:\temp\217\CTI\Ephone_DIT_Deploy\Binaries\Debug\EPhone.DataModel.dll",
"x86". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take
a dependency on references with a processor architecture that matches the targeted processor architecture of your project.
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Microsoft.Common.targets (1605): There was a mismatch between the processor architecture of the project being built "MSIL" and the processor architecture of the reference "d:\temp\217\CTI\Ephone_DIT_Deploy\Binaries\Debug\EPhone.dll",
"x86". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take
a dependency on references with a processor architecture that matches the targeted processor architecture of your project.
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Workflow.Targets (121): Compilation failed. Unable to load one or more of the requested types. Retrieve the LoaderExceptions property for more information.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneReporting/EPhoneReporting.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneCallback/EPhoneCallback.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.DataModel/EPhone.DataModel.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.Workflow.Interface/EPhone.Workflow.Interface.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Ephone.Workflow/EPhone.Workflow.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol.CTIOS/Communications.Protocol.CTIOS.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Softphone.DelphiCallConn/Communications.Protocol.DelphiCallConn.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol.Proxy/Communications.Protocol.Proxy.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/ChannelIntegrator/ChannelIntegrator.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.DataModel/EPhone.DataModel.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.Workflow.Interface/EPhone.Workflow.Interface.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneReporting/EPhoneReporting.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Ephone.Workflow/EPhone.Workflow.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneCallback/EPhoneCallback.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneUserControl/EPhoneUserControl.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol/Communications.Protocol.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Softphone/Communications.Softphone.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/CTIException/CTIException.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/Common/Common.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/ChannelIntegrator/ChannelIntegrator.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.DataModel/EPhone.DataModel.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneMarcomApplication/EPhoneMarcomApplication.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneUserControl/EPhoneUserControl.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneCallbackApplication/EPhoneCallbackApplication.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneUserControl/EPhoneUserControl.csproj for default targets.
00:02
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneQueView/EPhoneQueView.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.DataModel/EPhone.DataModel.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Microsoft.Common.targets (1605): There was a mismatch between the processor architecture of the project being built "MSIL" and the processor architecture of the reference "d:\temp\217\CTI\Ephone_DIT_Deploy\Binaries\Debug\EPhone.DataModel.dll",
"x86". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take
a dependency on references with a processor architecture that matches the targeted processor architecture of your project.
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Microsoft.Common.targets (1605): There was a mismatch between the processor architecture of the project being built "MSIL" and the processor architecture of the reference "d:\temp\217\CTI\Ephone_DIT_Deploy\Binaries\Debug\EPhone.dll",
"x86". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take
a dependency on references with a processor architecture that matches the targeted processor architecture of your project.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Ephone.Tests/Ephone.Tests.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/ChannelIntegrator/ChannelIntegrator.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/Common/Common.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Softphone/Communications.Softphone.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.DataModel/EPhone.DataModel.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Ephone.Tests.CallGenerator/EPhone.Tests.CallGenerator.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol/Communications.Protocol.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Softphone/Communications.Softphone.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol.CTIOS.TestRunner/Communications.Protocol.CTIOS.TestRunner.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol/Communications.Protocol.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/CTIException/CTIException.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol.CTIOS.TestRunner/Communications.Protocol.CTIOS.TestRunner.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Ephone.Tests.CallGenerator/EPhone.Tests.CallGenerator.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Ephone.Tests.Runner/Ephone.Tests.Runner.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/Common/Common.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.DataModel/EPhone.DataModel.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Ephone.Tests/Ephone.Tests.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneIDD/EPhoneIDD.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Softphone/Communications.Softphone.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.DataModel/EPhone.DataModel.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/ChannelIntegratorTest/ChannelIntegratorTest.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/Common/Common.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/ChannelIntegrator/ChannelIntegrator.csproj for default targets.
CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor
MSBuild Log File
00:08
Generating list of changesets
00:20
Built Skins\SkinEPhone.cs for default targets.
Skins\SkinEPhone.cs (3838): The member 'EPhone.SkinEPhone._txtOrderNumber_TextChanged(object, System.EventArgs)' does not hide an inherited member. The new keyword is not required. [d:\temp\217\CTI\Ephone_DIT_Deploy\Sources\EPhoneUserControl\EPhoneUserControl.csproj]
C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets (3201): Unable to apply publish properties for item "microsoft.vbe.interop". [d:\temp\217\CTI\Ephone_DIT_Deploy\Sources\EPhoneWinForm\EPhoneWinForm.csproj]
C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets (3201): Unable to apply publish properties for item "stdole". [d:\temp\217\CTI\Ephone_DIT_Deploy\Sources\EPhoneWinForm\EPhoneWinForm.csproj]
C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets (4513): Item 'Microsoft.Net.Framework.3.5' could not be located in 'C:\Program Files (x86)\Microsoft SDKs\Windows\v8.0A\Bootstrapper\'. [d:\temp\217\CTI\Ephone_DIT_Deploy\Sources\EPhoneWinForm\EPhoneWinForm.csproj]
Skins\SkinEPhone.cs (3838): The member 'EPhone.SkinEPhone._txtOrderNumber_TextChanged(object, System.EventArgs)' does not hide an inherited member. The new keyword is not required. [d:\temp\217\CTI\Ephone_DIT_Deploy\Sources\EPhoneUserControl\EPhoneUserControl.csproj]
C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets (3201): Unable to apply publish properties for item "microsoft.vbe.interop". [d:\temp\217\CTI\Ephone_DIT_Deploy\Sources\EPhoneWinForm\EPhoneWinForm.csproj]
C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets (3201): Unable to apply publish properties for item "stdole". [d:\temp\217\CTI\Ephone_DIT_Deploy\Sources\EPhoneWinForm\EPhoneWinForm.csproj]
C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets (4513): Item 'Microsoft.Net.Framework.3.5' could not be located in 'C:\Program Files (x86)\Microsoft SDKs\Windows\v8.0A\Bootstrapper\'. [d:\temp\217\CTI\Ephone_DIT_Deploy\Sources\EPhoneWinForm\EPhoneWinForm.csproj]
C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\TeamBuild\Microsoft.TeamFoundation.Build.targets (1740): TF201077: The work item type Bug cannot be found. It may have been renamed or destroyed.
C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\TeamBuild\Microsoft.TeamFoundation.Build.targets (1740): The "CreateNewWorkItem" task failed unexpectedly.
Microsoft.TeamFoundation.WorkItemTracking.Client.WorkItemTypeDeniedOrNotExistException: TF201077: The work item type Bug cannot be found. It may have been renamed or destroyed.
at System.Activities.WorkflowApplication.Invoke(Activity activity, IDictionary`2 inputs, WorkflowInstanceExtensionManager extensions, TimeSpan timeout)
at System.Activities.WorkflowInvoker.Invoke(Activity workflow, IDictionary`2 inputs, TimeSpan timeout, WorkflowInstanceExtensionManager extensions)
at Microsoft.TeamFoundation.Build.Tasks.WorkflowTask.ExecuteInternal()
at Microsoft.TeamFoundation.Build.Tasks.Task.Execute()
at Microsoft.Build.BackEnd.TaskExecutionHost.Microsoft.Build.BackEnd.ITaskExecutionHost.Execute()
at Microsoft.Build.BackEnd.TaskBuilder.<ExecuteInstantiatedTask>d__20.MoveNext()
00:03
Creating work item
Exception Message: TF270015: 'MSBuild.exe' returned an unexpected exit code. Expected '0'; actual '1'. See the build logs for more details. (type UnexpectedExitCodeException)
Exception Stack Trace: at System.Activities.Statements.Throw.Execute(CodeActivityContext context)
at System.Activities.CodeActivity.InternalExecute(ActivityInstance instance, ActivityExecutor executor, BookmarkManager bookmarkManager)
at System.Activities.Runtime.ActivityExecutor.ExecuteActivityWorkItem.ExecuteBody(ActivityExecutor executor, BookmarkManager bookmarkManager, Location resultLocation)
Final Property Values
BinariesSubdirectory =
BuildDirectory = d:\temp\217\CTI\Ephone_DIT_Deploy
CommandLineArguments =
ConfigurationFolderPath = $/CTI/DEV/DEV_INT/source/TeamBuildTypes/EPhone_DIT
DoNotDownloadBuildType = False
LogFilePerProject = False
MaxProcesses = 1
NodeReuse = False
RecursionType = OneLevel
SourcesSubdirectory =
TargetsNotLogged =
TestResultsSubdirectory =
ToolPath =
ToolPlatform = Auto
Verbosity = Diagnostic
Final Property Values
Condition = True
Final Property Values
MaxExecutionTime = 00:00:00
MaxWaitTime = 04:00:00
ReservationSpec = Name=*, Tags=
Result = U4VMDWODBDEV03 - Agent1 (vstfs:///Build/Agent/217)
Final Property Values
AgentSettings = Use agent where Name=* and Tags is empty; Max Wait Time: 04:00:00
BinariesSubdirectory =
ConfigurationFolderPath = $/CTI/DEV/DEV_INT/source/TeamBuildTypes/EPhone_DIT
DoNotDownloadBuildType = False
LogFilePerProject = False
MSBuildArguments =
MSBuildPlatform = Auto
RecursionType = OneLevel
SourcesSubdirectory =
TestResultsSubdirectory =
Verbosity = Diagnostic
Please have a look and guide where to find a problem
Thanks ahead

Hi Hooi,
I'd like to know whether you can build successfully in your local machine with MSBuild. You have to build succeed with MSBuild beore you can build with TFS Build since TFS build use MSBuild as its default compiler.
From the error message, you might build with wrong platform for your project. Please check if the build platfrom is proper. If you have customization of your build process template, it would be better to elaborate the reproduce steps and customization details.
Best regards,

FWTR056 Error assigning update type to flow type 1200, sign -

Hi
we have defined a monymarket product type 530 ("Repo") with Transaction Type 200 (Liablity) and 100 (Asset). This works fine.
Now, the current market situation requires negative interests for Transaction Type 200:
Example:
First Cashflow: +1M
Final Repayment: -1M
Interest: +Interest (Sign!)
So, we get the interest Cashflow at the end.
I have assigned the Condition 1200 used for TransactionType 100 also to ConditionType 200.
After using FTR_CREATE for Producttype=530 and TransactionType=200, I can correctly choose between the 2 Conditions 1200 and 1205.
But: after choosing 1200, the cashflow is shown negativ (althow I have assigned Direction "+" when assigning flowtype to update type 1200)
Also: when I try to save the deal, I get "FWTR056: Error assigning update type to flow type 1120, sign +, contract type 5"
Any ideas how to solve this or to define negative interests? It really should be an interest cashflow, not an "other flow".
Regards, Cornel

Here the Response from SAP (in german): negative Interests are not possible (or only by using a workaround..)
04.08.2011 - 16:53:16 CET - Antwort von SAP
Sehr geehrte Damen und Herren,
im Standard ist die Berechnung mit negativen Zinsen aus technischen
Gründen nicht möglich.
Leider kann die Funktionalität nicht im Rahmen des Supports erweitert
werden, somit muss ich Sie mit Hinweis 11 vertrösten.
Eventuell könnten Sie es mit einem Workaround probieren:
1. Temporär die entsprechenden Positiv-Beträge für Zinsen
nutzen, aber die Kontierungen umdrehen (das wäre aber umständlich
und würde für Zinskapitalisierung nicht gehen),
2. oder die Geschäft mit einer variablen Zinsenreferenz anlegen und
dann die Konditionen für die betroffenen Perioden mit einem
passenden Abschlag (Spread) erzeugen,
3. oder eben negative Zinsen als Null-Zinsen erzeugen und für diese
Perioden Bewegungen manuell anlegen (als Zusatzbewegungen).
Ich kann Ihnen hier leider keine positivere Antwort geben.
Mit freundlichen Grüßen,
XY
FIN Senior Support Consultant
AGS Primary Support, Business Suite & Technology
SAP AG

Posting log for source flow type/update type

Similar Messages

Maybe you are looking for