Derivation of subassignments in reclass posting

Dear experts,
I faced with the following problem with Reclass posting in SEM-BCS: I've profit center as a subassignment, and during reclass posting the profit center value is not derived from the trigger. Break down category settings is requred breakdow with default value, and I have default profit center instead of the profit center from trigger.
Have youany idea what the reason could be? Could be a matter of the method layout?
Thanks in advance,
Oleg

Solved, reclass is done on 10 PL, I've restricted trigger with PL 00, 01.

Similar Messages

Automatic derivation of service tax (derived flow) flow during the posting of charges through FWBS in Security Module.

Hi
Case: Automatic derivation of service tax (derived flow) flow during the posting of charges through FWBS in Security Module.
I am trying to post the charges using Manual Posting FWBS but system not generating (automatically) derived flow for the service tax flow on charges.
I have done below mentioned steps for configuration:
Define the derivation procedure and Rules.
Assign the update type to the function of security account management.- Define update type fo manual posting.
Kindly advise.
Regards

Hi,
The definition of "Define Derivation Procedures and Rules" for derived flows are only taken into account during transaction management, deriving one flow type from origin flow type. This customizing does not have effect for FWBS. You may check the below customizing:
1) Transaction Manager > Securities > Master Data > Product Types > Define Company Code-Dependent Settings for the Product Type: mark the indicator "Generate taxes" in Settings for tax generation.
2) Transaction Manager > Securities > Position Management > Securities Account Management > Define Tax Rates.
Further you may consider the implementation of BAdI TPM_TAX_CALCULATION (please see note 1159408) to calculate the tax depending on your requirements. Note: the above BAdI is called only in the case the required settings are done in 'Define Tax Rates' in the Customizing.
Best regards,
Jasmine

Derivation rule to maintain while posting physical inventory diff

Hi SAP GURUS,
Could you please me its very urgent!
My user are doing the monthly physical inventory,but for some components,when they are tring to post the physical inventory diff ,its giving an error " ERROR OCCUR IN THE DERIVATION RULE" .
Please suggest me where i need to maintain this derivation rule for the fsource field.Thanks in advance.
Regards
Reddy

Check with the Movement type useing for that posting the Physical diff and also check the document for the same.

Profit Ctr derivation for under payment auto posting in F-28

Hello,
I'm trying to apply a customer short payment to an open AR invoice in F-28. We have a 10% tolerance so the invoice is being cleared and remainder booked to the underpayment account. However, this is a revenue series accounts and requires a profit center but SAP is not able to derive the profit center for this account. I was expecting it to find the same profit center that was booked on the AR line of the invoice after splitting.
So, here is the process.
When Billing/AR invoice is posted in SAP either via the billing document in SD or directly in FI, SAP books the following posting.
Debit Customer/AR (No Profit Center at the time of posting)(Entry view)
Credit Revenue (Profit Center is a required field and populated either from the Billing Doc. material or manually in FI)
When this invoice above is saved, new GL Splitting functionality stamps the profit center from the Revenue line on to the Customer Line, so user will see the following. Note that this functionality is working fine.
Debit Customer (Profit Center from the Revenue Line)(GL View)
Credit Revenue (Profit Center from Billing Doc)
When the incoming cash is applied to the customer invoice above in F-28, if the Tolerances are setup, SAP books the following entry.
Debit Cash/Bank (No Profit Center)
Debit Under Payment (No Profit Center)
Credit Customer (Profit Center from the invoice)(GL View)
Now, when splitting process is done, I am expecting the profit center from the AR line(derived from the original invoice) to be stamped to the Underpayment and Bank Account lines but that is not happening.
I don't want to setup defaults in FAGL3KEH or specify profit center manually as short pay should go back to the same profit center that the invoice was generated in.
Any suggestions or pointers are greatly appreciated.
Thanks much for your time
Sumit

Pankaj,
Thanks much for the reply. I have checked this configuration multiple times and everything is in order but still, SAP refuses to tag the profit center on the under payment account.
Have you ever come across this business requirement at any client and if yes, were you able to achieve it via splitting? To me, it seems, SAP is not equipped to handle it since this is not a straight forward splitting. SAP needs to first look at the invoice number at the time of cash application, go back to that invoice and look at the profit center assigned to the AR line after spitting and then, assign it to the short pay account.
Thanks much for your time.
Sumit

Derivation Strategy for billing types - Post activation in KE4W

Dear Friends,
I recently activated KE4W for billing types S2, Credit Notes & Debit notes.
This is for restricting the COGS flow to CO for these billing types.
Now when i am releasing the sales document to accounting - Its asking to maintain derivation strategy.... KEDR for all the billing types.
From my previous implementations i have never maintained KEDR for billing types... as it is suppose to be on a standard derivation strategy.
How can i go about resolving this.
Do i at all need to maintain KEDR for billing types.. or is this error because of something else..
Thanks in advance
Vikrant Sood.

HI,
normally KE4W (reset CO-PA value fields) does not require any KEDR-steps.
I suggest to make a test derivation within KEDR to identify the step(s) where the message occurs.
Maybe also T-Code KECM is helpful (Overview of derivation, characteristic derivation) to see if the billing type is used as a key field,...
Best regards, Christian

Derived Flow block for posting in Product Type 55A

Dear SAP Gurus,
Kindly request your input issues that I have.
Currently I'm maintaining a derived flow type on Product Type 55A (Interest Rate Instrument) and Product Type 56B (Syndicated Facility).
The derived flow were used to generate withholding tax flow type. The source flow is maintain manually as Other Flows.
The derived flow for both Product Type 55A and Product Type 56B were successfully generate. But on Product Type 55A the derived flow were block for posting, the reason is because the 'Previous Flow does not permit for posting'.
What confused me why this block is not happening on Product Type 56B, while I use the same flow type and how to UNBLOCK the flow type so its open for posting again.
Thanks for the input before.
Cheers,
Tedi

Hi,
In the configuration setup check your flowtype and see whether Calc with Capital Reduction checked. I believe by default SAP has this checked; uncheck it. When this option is checked, it doesn't allow you to make any modifications to the contract if a posting has already occurred. e.g. increasing or decreasing the nominal amount of the contract.
Hope that helps.
-Anya

How to derive Budget Period from Delivery date in PR/PO

Hello Gurus,
I have activated the Budget Period functionality in FM (BCS). I am deriving the budget period from Posting date but in case of PR/PO I want to derive it from Delivery date instead of Document/Posting Date.I know it is not possible while standard derivation. Could any one help me with some suggestion like if I can use some exit/BaDI in MM. Also I am creating a PM order and at the time of release of PM order system creates the PR in background hence I need to know some kind of exit/BADI which can be called to update the Budget Period field in PR.
Thanks in Advance!
Regards
Rohit Goel

Hello Eli,
I have one more query to ask on the above scenario.
The scenario is my delivery date in PO is say July but I did good issue in May hence the Budget Period should be May and not july in my GR and IV.
Now when I am doing GR in May then system is showing the Budget Period as July in GR document but in FM Document it is populating as May. I have defined a derivation strategy to derive budget period from posting date so may be because of that.
But when I am doing IV then it is again moving the amount from May to July. It may be right behaviour that system is deriving all the account assignment from Source document but is there any way to overwrite.
I have defined the derivation strategy with the condition that overwrite with new value if already written (Deriving from Posting Date to Budget Period).
Please guide me on this if possible.
Thanks in Advance
Regards
Rohit

WBS derivation through FMDERIVE in goods issue

Hi all,
For a unique goods issue scenario, we are trying to derive the WBS element based on valuation class in a goods issue posting through the MB1A transaction. In the test mode of FMDERIVE and activating the 'trace' feature in FMDERIVE, the WBS element is being derived and populated in the WBS element field. However, when the goods issue is posted and the accounting document is viewed, the WBS element field is EMPTY. We have tried really hard to figure out what is going on, but to no avail.
In one of the other postings, I found reference to a function module (PSPNUM_EXTERN_TO_INTERN_CONV) that changes the wbs element from an external number to an internal number - I do not know how this works or what exactly this does. Furthermore, i dont see this function module in our list in fmderive. What we do have is FMDT_CONVERSION_WBS_INT_TO_EXT - can i use this instead? What does this do?
If i were to use this function module what would the source and target fields be?
Can one of you please help?
Are there any other ways to accomplish this? or is it a standard functionality that WBS element is not derived in a goods issue posting?
Please let me know.
PSM

Hi,
FMDERIVE is used for FM documents basically to derive FM assignment based on the FI/CO/LO attributes of the original document. You cannot use this functionality if you want to substitute the value in FI/CO documents. For this, use FI (OBBH) or CO (OKC9) substitutions.
Regards,
Eli

FF67-Business Area Automatic Derivation

Dear Experts,
We have activated Business Area wise balance sheet. Kindly let me know if there is any possibilities of deriving Business Area automatically in FF67 from the Payment Document no entered in "Bank Reference.
Thanks !

Hi Manya,
I am not clear about your Question..in BRS-FF67, if you are using post with clearing for posting Area 2 and interpretation algorithm, then system will itself look for the Business Area in the posted document of either incoming/Outgoing Document and that Business Area would get derived for Main Bank Account posting based on Document Splitting Principles.
But in case you want to achieve what you have stated for valid reasons that you may have, use User EXIT in Substitution and write your logic for derivation in the Exit.
Regards,
SAPFICO

0FISCPER is not being derived from 0FISCPER3 and 0FISCYEAR

We are attempting to derive Fiscal year/period from posting period and fiscal year within our BPS planning application. This seemed pretty straightforward.
We are using a standard FM provided by SAP (UPF_TIME_EXIT_FISC_DERIVE).
The source is specified with both posting period (0FISCPER3) and fiscal year (0FISCYEAR) with the target being 0FISCPER fiscal period/year.
I put in a break point, ran a copy function, but did not reach the break point, and the derivation did not occur.
I cannot add 0FISCVAR Fiscal year variant to the source characteristics since it is a constant in the cube.
Is 0FISCVAR not being included preventing us from deriving 0FISCPER?
Is there a way around this issue?
Any other ideas on how to get this to work and why it's not working?
thanks for your time in advance.
Edited by: Cindy Burlet on Dec 5, 2008 6:14 PM

Hi,
Even i agree with Gregor that Variant is not a problem;
Please check why you are not getting a break point when you are executing the function;
How have you designed you function ?
Generally when there is not data available for your selection , we don't get a break-point;
please select characteristics values for which data is available or you can hard-code the "BREAK-POINT" to be doubly sure and use external break-point for it.
Debug will give you a brighter picture about your input n output values from th STD SAP function.
Thanks
Pratyush

TPID not Derive from Intracompany Asset Transfer

Hi,
I'm facing a problem with Intracompany asset transfer ~ Trading Partner is not auto derive from the asset transfer posting.
Currently I'm using a customize transfer variant (copy from transfer variant 4). The only difference is that the customize one do not copy the original master data details (cost ctr, plant, etc) to a new asset.
Is there any other way that I can use to make the TPID automatically derive from this transaction?
TQ.

Hi,
check the transfer variant concerning the Transfer of Fields for new Assets in Target Company Codes. IMG Asset Accounting -> Transactions -> Intercompany Asset Transfers -> Automatic Intercompany Asset Transfers -> Define Transfer Variants. On the popup choose "Specify Transfer of Fields (for New Asset in Target CoCd)" ... here you can set up which fields are taken over, when you create new assets within the transfer posting.
Regards,
Markus

Error while doing miro of network purchase order ( no funds center entered/

Hi,
we are facing one problem while doing miro of network service purchase order. System is giving message 'No funds center entered/derived in item 00030'.
We have activated funds management in Jul'10. The said network service PO belong to previous year. Also we have changed
commitment item of GL account related to concerned service order in Jul'10 & posted GRN one in apr'10 & one aug'10.
System is not allowing to cancel the service entry sheet.
Can anybody help on this.
regards
abhishek

we had activated the trace facility for FMDEIRIVE & found that all FC/Commitment item derived correctly. But while posting the document it is throwing an error.
Regards
Abhishek

Table K9RAAANNNNNNN is not active in the system Message no. K/066

Good Morning SAP Guru's-
I am having an issue during our SAP Upgrade from SP12 to SP18 for my client. While testing creating a billing document via t-code VF01, we received the above issue which resulted in a Syntax error. It appears we are missing a table? Initially, I thought activating the operating concern via KEA0 would be the solution as the same table is found in our sandbox and it works there.
Table RKEAK9R
I am not an COPA expert however I do not understand why or what is the solution to fix this. I found notes in SAP but they did not resolve the issue.
Is there something I need to activate in development or ?
Many thanks!!
Edited by: CharlesMM on Jan 19, 2011 5:08 PM

Hi
This table is created in COPA when you create a derivation step in KEDR using "Derivation rule"... The values that you maintain are maintained in this K9RAA... table...
Ensure if your derivation rules are maintained properly post upgrade and try to regenerate your operating concern from KEA0
Notes 446279 or 148609 may be useful
BR, Ajay M
Edited by: Ajay Maheshwari on Jan 19, 2011 9:58 PM

Verizon Community Terms of Service 3/24/2015

Your use of the Verizon Community (Forums, Blogs, and Idea Exchange) is governed by these Verizon Community Terms of Service, together with the Verizon Privacy Policy and Verizon Terms of Use (collectively, the "Terms"). The Terms describe the permitted and prohibited uses of Verizon Community, among other things. Your access or use of Verizon Community evidences your acceptance of the then-current version of the Terms, and any related rules and guidelines posted on Verizon branded web sites.
Verizon reserves the right to modify the Terms at any time, effective upon posting of the modified Terms on Verizon Community or, in the case of the Verizon Privacy Policy or the Verizon Terms of Use, on any other Verizon sponsored Web site. Verizon also reserves the right to apply, waive, or modify these Terms as they apply to a specific posting and user without affecting the application of these Terms to all other postings and users.
"Posting" means, but is not limited to, any text, links, images, communications, opinions, software, data, and any other content any person provides on Verizon Community, including, but not limited to message boards, chats, blogs, or otherwise. Your use of Verizon Community, or any materials or services accessible through it, after a Posting or notification regarding modifications to the Terms constitutes your acceptance of those modifications. Your violation of any of the Terms may result in the suspension or termination of your access or use of Verizon Community.
Participating in the Verizon Community
The Verizon Community is intended to provide consumers with the opportunity to exchange useful and helpful information. All participants must be above the age of eighteen. We may edit or remove any posting we consider, in our sole discretion, to violate the Terms or be inappropriate for the Verizon Community for any reason.
Appropriate Conduct
Users of the Verizon Community are responsible for exercising careful and appropriate judgment in evaluating and taking action based on other participants' postings on Verizon Community, since such postings may reflect significantly different levels of knowledge and experience by participants. Users of the Verizon Community agree that Verizon is not responsible for the accuracy of the content of the Verizon Community and will not be liable for any damages incurred as a result of their use of any such content. Participants may post hypertext links to content hosted and maintained by third parties. Verizon has no obligation to monitor these linked sites, and is not responsible for them. Accessing any such linked sites is done entirely at the user's own risk.
Posting to the Verizon Community
Users of the Verizon Community agree not to upload, post, or otherwise transmit any content (including but not limited to text, links, communications, software, images, sounds, data, or other information) that includes any of the following inappropriate content:
Any personal information belonging either to the poster or another person, such as full name, address, phone number, personal email address, chat ID numbers, router serial numbers and trouble ticket repair numbers. Also no phone/fax numbers, emails, for any business or their employees;
Spam such as advertisements for other web sites and services, chain letters, or pyramid schemes, unauthorized solicitation;
Flood, such as excessive posting or padding posts;
Profanity; material that is libelous, fraudulent, unlawful, defamatory, pornographic, obscene, profane, abusive, offensive, threatening, hateful, or otherwise objectionable;
Discussion of illegal activities or providing links to other websites containing such information;
Discussions that veer off topic, are unrelated to resolving the issue at hand, or abuse any company or product.
Discussions of moderator actions on the boards. If you need to comment on a moderator action, please private message any administrator/moderator;
Material, the posting of which violates any party's copyright or other intellectual property rights;
Posting, publishing, uploading, reproducing, transmitting or distributing in any way any content belonging to Verizon, or derivative works with respect thereto;
Posting or transmitting any information or software containing a virus, worm, Trojan horse, or other damaging or destructive component;
Posting a link directing users to any information or content that, if posted on the Verizon Community, would constitute a violation of the Terms or of any State or Federal law;
"Bombing" the Verizon Community or individual threads with repetitive or meaningless postings, postings unrelated to the purpose of the Verizon Community, excessive cross-posting; "bumping" or making posts with no new useful content in order to move them to the top of the subject area.
Attacks, including "Flaming" another user or entity in such a way as to incite or perpetuate an argument or conflict; creating usernames to attack other users' identities; impersonating other individuals or falsely representing one's identity or qualifications; posts made under secondary user names or other aliases for the purpose of either endorsing or denigrating others; posts that breach any participant's privacy by including name, address, phone, email address, or any other identifying information.
Posts that describe how to violate Verizon policies or terms or conditions are considered unacceptable and will have the offensive language deleted.
Posts that discuss hacking and/or rooting a wireless phone from any carrier will be removed.
Posts that discuss how to circumvent Verizon’s security.
Posts that discuss any litigation or potential litigation (past, present, future or otherwise) is prohibited since the Verizon Community forum is not a legal venue.
Kudos abuse including soliciting others for kudos, or giving an excessive number of kudos to a specific user.
User may not repost any private communications they have had with Verizon agents or staff on the boards.
If a user posts a thread threatening Verizon with Legal action, that post will be removed so it can be reviewed by the appropriate teams within Verizon. The user will be sent a PM to be notified of this action and the resolution.
Small business customers may provide information about the company in a post or profile, e.g “We sell phones. Click here to learn more about our phones and our company.” However small business customers may not spam or advertise specific offers, e.g. “We sell phones. Click here and for $19.99 you can buy our phones.”
Please Note: Verizon reserves the right to remove or move any posts or any profile content either deems inappropriate.
Idea Exchange License
You grant to Verizon and its designees a worldwide, perpetual, irrevocable, non-exclusive, sublicensable, transferable, fully-paid up and royalty free license to use (i) any ideas, expression of ideas or other materials you submit to the Verizon Community (collectively, "Materials"), and (ii) any and all intellectual property rights you have that cover or are in any way related to the Materials, whether in patent, copyright, trademark, trade secret, or any other proprietary right, in each case without restrictions of any kind and without any payment or other consideration of any kind, or permission or notification, to you or any third party (the “License”).
The License shall include, without limitation, the right to reproduce, prepare derivative works, combine with other works, alter, translate, distribute copies, display, perform, and sublicense the Materials, and own all rights therein in the name of Verizon or its designees, throughout the universe in perpetuity in any and all media now or hereafter known. The License shall also include the right to, directly or indirectly (including through multiple layers of persons/entities), make, have made, use (including by Verizon customers), sell, offer for sale, import, distribute, and otherwise dispose of any product or service that includes any ideas, inventions, embodiments, or other concepts that are part of the Materials, and use any and all intellectual property rights you have related to such Materials. The License shall also permit Verizon and its designees to use the Materials (including portions thereof), rerecord or modify any audio tracks or visual images you provide, rewrite any Materials you submit, and/or incorporate other materials, either created by Verizon and its designees or any third party, with the Materials you submit. Any such works shall be owned by Verizon and shall not be subject to your approval or payment by Verizon of any compensation to you.
You agree that the Materials you submit: (i) are original to you and accurate, (ii) do not violate and will not violate the rights of any third party or any local, state, national or foreign law, including any right of publicity, right of privacy or any other proprietary right, (iii) are owned by you and are not subject to any claim of ownership by your current employer, a former employer, or any third party, (iv) do not contain the confidential information of any third party, and to the extent they contain your confidential information, immediately become non-confidential the moment you submit the Materials to the Verizon Community; and (v) are submitted by you on your personal behalf, and not on behalf of your employer or any third party. You also agree that you have filed to protect and/or preserve any protectable ideas contained in the Materials, to the extent you wish to protect and preserve them (e.g., through copyright registration, patent application filing, etc.) prior to your submission of such Material to the Verizon Community.
You acknowledge and agree that the relationship between you and Verizon is not a confidential, fiduciary, or other special relationship. We shall have the right, but not the obligation, to use your name, likeness, biography and other information about you in connection with any use of the Materials you submit.
By making a submission, you acknowledge and agree that Verizon and its designees (i) are continually and independently of the Materials working on ways to improve upon and expand Verizon’s product and services offerings, and may create on their own new products or services that are similar to the Materials, (ii) obtain many submissions from others that may be similar or identical to the Materials you submit through Verizon Community or other channels and means. You hereby waive any and all claims you may have had, may currently have, and/or may have in the future related to Verizon’s review, acceptance, and/or use of the Materials, (iii) are under no obligation to review, use, or in any way process your Materials, regardless of the status indicated on the Verizon Community.
Registration Requirements
While registration is not required to read postings on the Verizon Community, users must register an account with Verizon in order to post to the Verizon Community. Verizon may refuse to grant you, and you may not use, a user name that is already being used by someone else, belongs to or impersonates another person, violates the intellectual property or other rights of any person (including but not limited to trademark rights), is offensive, or that Verizon rejects for any other reason in its sole discretion. Participants agree that all information provided in a profile is accurate, up to date, and complete, and that it will be kept updated. Verizon may terminate your account if any of the information provided is found to be inaccurate, out of date, or incomplete.
Privacy Concerns
Verizon strongly discourages users from posting personally identifiable information in the Verizon Community. Any information posted on the Verizon Community is at the user's own risk. Verizon respects and protects the privacy of our customers and those who use our Web sites, and the Verizon Privacy Policy provides details of our approach to privacy and how we collect, use and protect personal information. But information posted on the Verizon Community is not protected and can be easily obtained and used by others.
Moderators
Verizon reserves the right to manage the postings on the Verizon Community to provide an orderly presentation of this information. To effectively manage the Verizon Community, Verizon may designate employees or others to act as moderators and administrators for the Verizon Community ("Moderators"). These Moderators are the only representatives of Verizon authorized to manage the Verizon Community. Any Verizon employees who are not designated as Moderators or Employees are not authorized to represent themselves on the Verizon Community as Verizon employees. Authorized Verizon Employees are distinguished by the Rank of "Employee" and/or an official Verizon logo as an Avatar. Verizon is not responsible for content provided by any Verizon employee who is not designated as a Moderator or an Employee.
Community Monitoring
Users are asked to help Verizon keep the Verizon Community a valuable and enjoyable information resource for all participants by notifying us of any offending messages or other violations of these Terms. To advise us of such a posting, click the confidential "Report Inappropriate Content" link on the applicable post. Repeat offenders will be contacted by email and eventually banned from the Verizon Community. If violations are egregious in nature, we will contact the appropriate authorities.
Modification and discontinuance of the Verizon Community
Verizon reserves the right at any time to delete, modify, suspend, or discontinue, temporarily or permanently, the Verizon Community (or any part of the Verizon Community, including any postings) with or without notice. Users agree that Verizon will not be liable to users or third parties for any modification, suspension, or discontinuance of the Verizon Community.
Termination
A user's privilege to utilize or access the Verizon Community may be terminated by Verizon immediately and without notice if the user fails to comply with any term or condition of the Terms. Upon such termination, the user must immediately cease accessing or utilizing the Verizon Community and agree not to re-register or otherwise make use of the Verizon Community. Furthermore, the user acknowledges that Verizon reserves the right to take action -- technical, legal, or otherwise -- to block, nullify, or deny the user's ability to access the Verizon Community. The user understands that Verizon may exercise this right in its sole discretion.
Disclaimer of Warranties and Limitation of Liability
MOST OF THE CONTENT POSTED TO THE VERIZON COMMUNITY IS PROVIDED BY THIRD PARTIES NOT AFFILIATED WITH VERIZON. THIRD-PARTY CONTENT IS THE SOLE RESPONSIBILITY OF THE PERSON ORIGINATING THAT CONTENT. THE USER AGREES THAT VERIZON DOES NOT CONTROL, AND IS NOT RESPONSIBLE IN ANY WAY FOR, THIS THIRD-PARTY CONTENT. ADDITIONALLY, THE USER AGREES THAT VERIZON IS NOT LIABLE FOR, AND THE USER SHALL INDEMNIFY AND HOLD VERIZON, AND ITS SUBSIDIARIES, AFFILIATES, OFFICERS, AGENTS, AND EMPLOYEES HARMLESS FROM ANY CLAIM, INCLUDING REASONABLE ATTORNEYS' FEES, MADE BY ANY THIRD PARTY RELATING TO OR ARISING OUT OF CONTENT SUBMITTED, POSTED, TRANSMITTED, OR MADE AVAILABLE THROUGH VERIZON COMMUNITY, USE OF VERIZON COMMUNITY, VIOLATION OF THE TERMS OR VIOLATION OF ANY RIGHTS OF ANOTHER. THE CONTENT ON VERIZON COMMUNITY IS "AS IS" AND CARRIES NO WARRANTIES. VERIZON DOES NOT WARRANT OR GUARANTEE THE ACCURACY, RELIABILITY, COMPLETENESS, USEFULNESS, NON-INFRINGEMENT OF INTELLECTUAL PROPERTY RIGHTS, OR QUALITY OF ANY CONTENT ON VERIZON COMMUNITY, REGARDLESS OF WHO ORIGINATES THAT CONTENT. VERIZON DOES NOT WARRANT THAT VERIZON COMMUNITY IS SECURE, FREE FROM BUGS, VIRUSES, INTERRUPTION, ERRORS, OR OTHER LIMITATIONS. YOU EXPRESSLY UNDERSTAND AND AGREE THAT YOU BEAR ALL RISKS ASSOCIATED WITH USING OR RELYING ON THAT CONTENT. VERIZON IS NOT LIABLE OR RESPONSIBLE IN ANY WAY FOR ANY CONTENT POSTED ON OR LINKED FROM VERIZON COMMUNITY, INCLUDING, BUT NOT LIMITED TO, ANY ERRORS OR OMISSIONS IN CONTENT, OR FOR ANY LOSSES OR DAMAGE OF ANY KIND INCURRED AS A RESULT OF THE USE OF OR RELIANCE ON ANY CONTENT. TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, VERIZON AND ITS REPRESENTATIVES ARE NOT LIABLE FOR ANY INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES (INCLUDING DAMAGES RELATING TO LOSS OF BUSINESS, TELECOMMUNICATION FAILURES, LOSS, CORRUPTION, SECURITY OR THEFT OF DATA, LOSS OF PROFITS OR INVESTMENT, OR THE LIKE), WHETHER BASED ON BREACH OF CONTRACT, BREACH OF WARRANTY, TORT (INCLUDING NEGLIGENCE), STRICT LIABILITY, PRODUCT LIABILITY, OR OTHERWISE, EVEN IF VERIZON OR ITS REPRESENTATIVES HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES AND EVEN IF A REMEDY IS FOUND TO HAVE FAILED OF ITS ESSENTIAL PURPOSE. THE LIMITATIONS OF DAMAGES SET FORTH ABOVE ARE FUNDAMENTAL ELEMENTS OF THE BASIS OF THE AGREEMENT BETWEEN VERIZON AND THE USER.
Miscellaneous
The Terms are a complete statement of the agreement between you and Verizon, and set forth the entire liability of Verizon and your exclusive remedy with respect to your access and use of the Verizon Community. In the event of a conflict between these the Verizon Community Terms of Service and either the Verizon Privacy Policy or the Verizon Terms of Use applicable to Verizon, these Terms of Service prevail. The agents and employees of Verizon (including Moderators) are not authorized to make modifications to the Terms, or to make any additional representations, commitments, or warranties binding on Verizon. Any waiver of the Terms by Verizon must be in a writing signed by an authorized officer of Verizon and expressly referencing the applicable provisions of the Terms. Your privilege to use or access the Verizon Community may be terminated by Verizon immediately and without notice if you fail to comply with any of the Terms. Upon such a termination, you must immediately cease accessing or using the Verizon Community. If any provision of the Terms is invalid or unenforceable under applicable law, then it is to be, to that extent, deemed omitted, and the remaining provisions will continue in full force. The Terms do not limit any rights that Verizon may have under trade secret, trademark, copyright, patent, or other laws.
*If you feel you have a solicitation that should be posted to the Verizon Community Forums, please ask for pre-authorization by contacting Verizon at: [email protected] or you can reach out directly by private message to any official moderator or admin in the community.

Looks to me (and I haven't been advised on changes) that this is a customer protection. I don't know what the previous policy was, but this guarantees that if FiOS is no longer serviced in your area, you cannot be charged an early termination fee if there remains time left on your account. It seems obvious that you wouldn't be he held responsible in such a case, but this is just putting it in writing.
Brian K
Verizon Telecom
Fiber Solution Center
Notice: Content posted by Verizon employees is meant to be informational and does not supercede or change the Verizon Forums User Guidelines or Terms or Service, or your Customer Agreement Terms and Conditions or Plan.

SSIS 2012 Script Task to Get File Properties

Hello,
I researched on how to grab a file properties such as file size, file modified date, etc and I came across the following
link:
I followed exact steps and when I went to execute the package, I got the following error:
Below is the code:
// C# code
// Fill SSIS variables with file properties
using System;
using System.Data;
using System.IO; // Added to get file properties
using System.Security.Principal; // Added to get file owner
using System.Security.AccessControl; // Added to get file owner
using Microsoft.SqlServer.Dts.Runtime;
using System.Windows.Forms;
namespace ST_cb8dd466d98149fcb2e3852ead6b6a09.csproj
[System.AddIn.AddIn("ScriptMain", Version = "1.0", Publisher = "", Description = "")]
public partial class ScriptMain : Microsoft.SqlServer.Dts.Tasks.ScriptTask.VSTARTScriptObjectModelBase
#region VSTA generated code
enum ScriptResults
Success = Microsoft.SqlServer.Dts.Runtime.DTSExecResult.Success,
Failure = Microsoft.SqlServer.Dts.Runtime.DTSExecResult.Failure
#endregion
public void Main()
// Lock SSIS variables
Dts.VariableDispenser.LockForRead("User::FilePath");
Dts.VariableDispenser.LockForWrite("User::FileAttributes");
Dts.VariableDispenser.LockForWrite("User::FileCreationDate");
Dts.VariableDispenser.LockForWrite("User::FileExists");
Dts.VariableDispenser.LockForWrite("User::FileInUse");
Dts.VariableDispenser.LockForWrite("User::FileIsReadOnly");
Dts.VariableDispenser.LockForWrite("User::FileLastAccessedDate");
Dts.VariableDispenser.LockForWrite("User::FileLastModifiedDate");
Dts.VariableDispenser.LockForWrite("User::FileOwner");
Dts.VariableDispenser.LockForWrite("User::FileSize");
// Create a variables 'container' to store variables
Variables vars = null;
// Add variables from the VariableDispenser to the variables 'container'
Dts.VariableDispenser.GetVariables(ref vars);
// Variable for file information
FileInfo fileInfo;
// Fill fileInfo variable with file information
fileInfo = new FileInfo(vars["User::FilePath"].Value.ToString());
// Check if file exists
vars["User::FileExists"].Value = fileInfo.Exists;
// Get the rest of the file properties if the file exists
if (fileInfo.Exists)
// Get file creation date
vars["User::FileCreationDate"].Value = fileInfo.CreationTime;
// Get last modified date
vars["User::FileLastModifiedDate"].Value = fileInfo.LastWriteTime;
// Get last accessed date
vars["User::FileLastAccessedDate"].Value = fileInfo.LastAccessTime;
// Get size of the file in bytes
vars["User::FileSize"].Value = fileInfo.Length;
// Get file attributes
vars["User::FileAttributes"].Value = fileInfo.Attributes.ToString();
vars["User::FileIsReadOnly"].Value = fileInfo.IsReadOnly;
// Check if the file isn't locked by an other process
try
// Try to open the file. If it succeeds, set variable to false and close stream
FileStream fs = new FileStream(vars["User::FilePath"].Value.ToString(), FileMode.Open);
vars["User::FileInUse"].Value = false;
fs.Close();
catch (Exception ex)
// If opening fails, it's probably locked by an other process
vars["User::FileInUse"].Value = true;
// Log actual error to SSIS to be sure
Dts.Events.FireWarning(0, "Get File Properties", ex.Message, string.Empty, 0);
// Get the Windows domain user name of the file owner
FileSecurity fileSecurity = fileInfo.GetAccessControl();
IdentityReference identityReference = fileSecurity.GetOwner(typeof(NTAccount));
vars["User::FileOwner"].Value = identityReference.Value;
// Release the locks
vars.Unlock();
Dts.TaskResult = (int)ScriptResults.Success;
Eventually I am looking to just grab the Modified Date from the Windows Explorer folder and insert into table. Any suggestions? Thank you in advance!
Sanjeev
Sanjeev Jha

Hi SSISJoost,
I am so glad you responded to this thread. You are absolutely right. I copied the entire code including the project name (guid) and that solved the error problem.
Now, what did you do to get the message box? I added the watch and I could see the values but how do I get these values in a table? If I remember correctly, in your blog, you mentioned something about using derived columns. I am familiar with Derived Columns
but how do I do that? I appreciate your response.
Thank you.
Sanjeev
Sanjeev Jha
I used a second script task to show all variable values. It has a
MessageBox in it and between all
variables I added a
newline to make it more readable...
But with an Execute SQL Task and parameters you can also put these values in a Table... or you can read the file in a Data Flow Task and add those variables (as metadata) to each record with a Derived Column
Please mark the post as answered if it answers your question | My SSIS Blog:
http://microsoft-ssis.blogspot.com |
Twitter

Derivation of subassignments in reclass posting

Similar Messages

Maybe you are looking for